Skip to main content

No use of AWTEventListener?

2 replies [Last post]
Joined: 2006-09-17

I've finally started to check out JXLayer, and wanted to understand how it works. One thing that puzzles me right away, is that it states in the JavaDoc of JXLayer:

Note: {@code JXLayer} is very friendly to your application, it uses only public Swing API and doesn't rely on any global settings like custom {@code RepaintManager} or {@code AWTEventListener}.

.. while LayerEventController, which seems to be the mechanism by which the system picks up the events and fires them on the LayerUI, rather clearly implements AWTEventListener and installs it onto the ToolKit?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2005-09-05

Hello stolsvik

Implementing JXLayer without AWTEventListener was my initial goal,
however it turned out that my clever trick didn't always work

so I returned AWTEventListener and simply forgot to update the spec,
will do it soon


Joined: 2006-09-17

Okay, thanks for the clarification.

Then also the link at page:
.. pointing to
.. should be updated one way or the other.

Some thoughts after having explored this (and the Piet Blok TransformUI stuff) for a short while:

On the project page, it would be nice if the demo-launch buttons was accompanied with a smallish screenshot of the feature in action (or an explanation of what happens). E.g. the spotlight effect have never seemed to do anything for me - and I am still wondering about what it is intended to do, how it should look. A screenshot (or explanation) would have cleared this up.

Why are the plaf package called that? As far as I have deduced, this package has nothing to do with the "plaf" packages, nor ideed for the concept, in Java (in one sense, one could say that it is directly the opposite: You can adorn your UI with looks and feels *across* the different laf's!). The same goes for "GlassPane". These names are so ingrained in the field where this project is directed that I can't seem to understand why you would want to "overload" them with rather orthogonal functionality?

Finally, the Piet Blok TransformUI and the JXLayer projects should be merged! :-)