Have you tried to wrapp the treeitem and then add the mouse listener to the wrapper? it should work like you want :)
On Jul 9, 3:32 pm, ProtoLD <[email protected]> wrote: > Is there any response on this? Working as intended...somehow? Even > though it doesn't work? > > On Jul 8, 4:03 pm, ProtoLD <[email protected]> wrote: > > > > > I need to add a mouselistener to my tree items that pops up a mini- > > menu to the side of the tree item. On this menu there will be 3 icons > > that are clickable with different actions. I'm not asking for someone > > to write this for me, I've done it about 30 times or so, but cannot > > get around IE/GWT browser issues. Honestly the IE issue is more > > important. The problem is this, if I apply the mouselistener to the > > table, it considers it a "mouseout" when moving over spaced out areas > > between the name and the new icons. An example is this: > > > (dashes are spaces) > > > ENCOMPASSING FLEXTABLE > > { XXXNAMEXXX---ICON1---ICON2---ICON3 } > > > If I move from "name" to "icon1" it acts as a "mouseout" in IE and the > > gwt browser (not in firefox, but I need IE for the job). This is > > using the sinkEvents method on the encompassing table. The same > > applies if I try doing it to the name icon alone, although for more > > obvious reasons. The second problem is, the Button class for whatever > > reason doesn't have a mouselistener, and the HTML class doesn't seem > > to respond nearly as well to clickevents after it's been reset a few > > times (because the icons should vanish when you go to another element > > or outside the tree). > > > I've looked at the Google quick-tips and tried applying the same > > knowledge here, but nothing seems to deal with the problems of adding > > multiple items on the same tree item as you mouseover and still having > > the mouselistener "mouseover" and "mouseout" events working > > correctly. If anyone has a solution for this problem...even (ugh) > > upgrading to 1.6 (I'm running 1.5.x), I will take it at this point. > > > The ONLY thing I have gotten to work even halfway decently is a timer > > that makes them disappear after two seconds, but this was deemed > > unacceptable unfortunately. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
