Slick Forums

I'm using this: http://wiki.l33tlabs.org/bin/view/TWL/U ... with+Slick

When I use mouse clicks or key presses, both Slick and TWL are getting the event. I'm calling the TWLInput update method in the Slick Render method.

Yeah,

I expected that I'm currently working on a solution.

As a work around you could handle all events in the TWL root pane instead of using a Slick input listener.

Ciao Matthias

_________________
TWL - The Themable Widget Library

Is there a way to detect/set focus on TWL windows?

yes, but it would be better to ask a new question in a new topic - otherwise it will be hard for others to find it

_________________
TWL - The Themable Widget Library

Just curious how this is going?



You mean handle everything in the TWLInputWrapper and then don't do anything with the Slick key capture methods? How do I tell if the input was meant for TWL or Slick?

A solution (which I had not yet time to really test) is to call Slick's Input.consumeEvent() when any of the GUI.handle* method returned true.

The other option is to override handleEvent() in the root widget you pass to GUI. Try something like this:

_________________
TWL - The Themable Widget Library

Doesn't the TWLInputWrapper already do that?

In TWLInputWrapper.java I have this:






I took this from the wiki/example:



So override it in TWLInputWrapper?




AppGameContainer doesn't have a handleEvent method.

http://slick.cokeandcode.com/javadoc/or ... ainer.html

No, the code on the wiki is wrong. Currently it consumes events when a popup is open - it should consume when GUI.handle* returns true:

But I did not have a Slick app around to play with such things. One major drawback with the above approach is that you must make sure that the TWLInputWrapper is always called first. For that you need to be careful in which order you add them to slick - esp once you start to remove things.

And the 2nd approach (which works always) is overriding the handleEvent method in the root widget. The root widget is the root parameter you pass to GUI:

Just replace the "new Widget()" with your own class which overrides handleEvent.

_________________
TWL - The Themable Widget Library

ok, this is setup. The only part is this:



I can't find mySlickGame.handleEvent(evt) in the API (AppGameContrainer or GameContrainer). Do I have to create my own and do something with it?

Of course, the intent behind the "mySlickGame" variable was to indicate that this calls your game logic.

_________________
TWL - The Themable Widget Library

So I have to put all my slick input handling in one method?
I'll look at it more tonight. If that is the case I'll have to try that first way again.

No, you can of course dispatch to other methods. TWL uses an Event object and a single handleEvent() method but this does not mean that all code has to be in that method.

Btw - did you try the 1st approach (calling input.consumeEvent() when GUI.handle* returned true) ?

_________________
TWL - The Themable Widget Library

ok. It'll take me a while to try this, as I have to rewrite a bunch of things. I handle everything in keyPressed or updates (in both States and in "Entities").




Yes. I updated to latest build of TWL.jar from website. I update both MousePress and MouseRelease and re-arranged the code (so twl update would be called first). The behavior was almost the same expect some TWL windows won't get focus.

The problem with calling twl input wrapper's update first (in render per the example) is that everything gets drawn over it. It is ok to break this up into update and render right? I put everything in update (called from slicks update) and in Render it's just the draw (called from slicks render).

I'm still playing with it and going to try a few more things.

ok, finally think I'm making some progress! thanks for your help.

I used your override method, but put in a pause/resume before/after the consumeEvent. That seems to be working:



edit: Seems to only work for mouse though, still need to figure out the keyboard events now.

edit2:

A little bit closer. This works with keyboard *if* the slick calls is:

input.isKeyPressed

If I use:
input.isKeyDown

it doesn't consume the event (even if it's just a quick tap on the keyboard). I think I need to handleRepeatKeys or such?


Example (in Slick update()):



doesn't work with the pause/consume/resume.

This *does* work though:



Unfortunately I don't see a KeyDown method that I can override:
http://slick.cokeandcode.com/javadoc/or ... apter.html

Any other way this could be dealt with?

input.pause() / resume() can't be right - don't do that.
Did you add this code pattern to all methods in the TWLInputWrapper ? or only to mousePressed?

isKeyDown() etc won't work - as this does not use an event based system. You have to use keyboard events (keyPressed/keyReleased).

_________________
TWL - The Themable Widget Library