🚀 go-pugleaf

Yes, I think that is how it is done. I dont think that you want to remove
the glassPane, it is just there doing nothing usually. Just remove your
mouse listener. If you consume the event , then it is eaten and the
underlying components dont see it.

James Cook <jimcook.remove.for.spam@iname.com> wrote in message
news:8hltut$5uf7@bornews.borland.com...
> Whoa! Fancy subject.
>
> I would like to implement context sensitive help on my Java screens, the
way it is sometimes done in Windows. They allow the user to
> click on a button (this I can do), the cursor changes (got it covered),
then the user clicks on a field, label, text, combo,
> whatever (don't know how), and a popup explains the feature (know how).
>
> I am unsure if can I detect a click on a field, without invoking that
field?
>
> See if this makes sense. When the user clicks on my "help" button, I
instantiate and place a glass pane on the form. The next click
> the user makes on the form is detected by the glass pane. Using some
built-in function to Frames (or Panels?), I ask for the
> component located at the mouse coordinates. After the click, the glass
pane is removed.
>
> Is this the best approach? Does it even work? Are there methods to support
it? GlassPane or LayeredPane? Will the underlying
> components be notified?
>
> thanks,
> jim
>
>