My conclusion:
Non-colliding functionkey detection can be done (find keycodes per
browser in tables or by manual experimentation).
Colliding functionkey detection should be possible using browser
plugins.
No existing W3 spec for DOM events.
For now: least work/max browser support, use the GWT
Thanks for the reply.
I did not read the supplied links, but I have read a number of
messages in this newsgroup regarding tricky keycodes,
however I have not seen a conclusion drawn from this.
Is the conclusion that KeyCodes vary between browsers and are therefor
not support in GWT ?
I think that it is not possible to use KeyCodes which are used by the
Browser. The root-instance which handles
KeyCodes is the Browser, this is the application which controls
everything you can see. When the Browser
has hardcoded that F5 is for reloading the content, so you can't use
this Key
i'm not 100% sure how this works, but will throw it out there in case
somebody knows or can figure it out.
the idea of a hot key was floated for my web app. on a forum a guy
offered to create browser plugins for my app that would be able to
capture function keys. here's some of the info he
Nice idea.
I think the new development mode a.k.a. hosted mode,
is implemented using plugins, so it might possibly be in the
sourcetree in a not too distant future.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
I can't find function keys (F1 - F12) in KeyCodes.*
Instead of:
NativePreviewHandler handler = new NativePreviewHandler() {
@Override
public void onPreviewNativeEvent(NativePreviewEvent
event) {
if
F1..F12 will probably return values of 112..123. But overall,
JavaScript key events are...interesting. Read this warning as here
there be dragons:
http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/gwt/event/dom/client/KeyEvent.html
Base class for Key events. The native
