Maybe, but I was using the Super simple... logging solution on the same
page. Unless something has changed in the logging infrastructure?
I have seen a post that claims some modules inherit the logging system and
disable it. It suggested putting the enable code at the bottom of the xml
file.
all. I never saw the URL change until just now and the embedded URL
in the code was, of course, the old one.
Thanks again, silly me
--
Dean Karres
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit
not implement ValueChange with different types message
again.
ideas are welcome
--
Dean Karres
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web
in the JSONArray so at the time of the button-click the
value of the JSONArray could be said to have changed. Once the
button is clicked the selection is cleared.
I think I will try this first and then go back to the logical handler
solution you suggested if necessary.
Cheers
--
Dean Karres
Just found this link which looks really good for ValueChangeListeners
http://lemnik.wordpress.com/2009/03/12/using-event-handlers-in-gwt-16/
--
Dean Karres
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google
Thank you.
On Tue, Jun 9, 2009 at 3:17 PM, Paulpaul.fuehr...@gmx.net wrote:
event.getSource()
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to