From: Jeremy C. <jc...@co...> - 2004-01-31 14:59:44
|
I want to trap the enter key on a given FXTextField. I associated an ID, inserted a FXMAPFUNC(SEL_KEYRELEASE,...). My function obviously runs whenever a key is released, but how do I tell what key was just entered? Thanks! Jeremy |
From: Lyle J. <ly...@kn...> - 2004-01-31 15:11:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 31, 2004, at 8:59 AM, Jeremy Cowgar wrote: > I want to trap the enter key on a given FXTextField. I associated an > ID, > inserted a FXMAPFUNC(SEL_KEYRELEASE,...). My function obviously runs > whenever a key is released, but how do I tell what key was just > entered? The data passed along with a SEL_KEYRELEASE message is a pointer to an FXEvent struct, and the "code" field of that struct holds the key code. So something like: long onKeyRelease(FXObject *sender, FXSelector sel, void *ptr) { FXEvent *event = reinterpret_cast<FXEvent *>(ptr); if (event->code == KEY_Return) { ... } return 1; } Hope this helps, Lyle -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFAG8WSFXV/hD6oMd0RAsUEAJ9mJE/wQbymO7HG26RmhKGxJmZCCQCfVbR0 FJsxiewhGnt85OZuEhv/gSI= =5mdU -----END PGP SIGNATURE----- |
From: Jeremy C. <jc...@co...> - 2004-01-31 15:26:54
|
On Sat, 2004-01-31 at 10:11, Lyle Johnson wrote: > The data passed along with a SEL_KEYRELEASE message is a pointer to an > FXEvent struct, and the "code" field of that struct holds the key code. > So something like: > > long onKeyRelease(FXObject *sender, FXSelector sel, void *ptr) { > FXEvent *event = reinterpret_cast<FXEvent *>(ptr); > if (event->code == KEY_Return) { > ... > } > return 1; > } > > Hope this helps, Lyle, That does help, but I have one more question. Did I miss this in the docs somewhere? I looked quite a bit and could not find it. Some things with FOX seem not to be documented very well yet and that's my only reason for asking. I am wondering if maybe their is another source for this information, or how you have come to learn this, that way, I can come to learn things the same way and coding will be much more productive :-) Thanks! Jeremy |
From: Lyle J. <ly...@kn...> - 2004-01-31 16:50:47
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 31, 2004, at 9:26 AM, Jeremy Cowgar wrote: > That does help, but I have one more question. Did I miss this in the > docs somewhere? I looked quite a bit and could not find it. Some things > with FOX seem not to be documented very well yet and that's my only > reason for asking. I am wondering if maybe their is another source for > this information, or how you have come to learn this, that way, I can > come to learn things the same way and coding will be much more > productive :-) The only reason you missed it is because it's not there ;) The documentation that does exist for FOX is very good; it's just that there's a lot of stuff that's still not documented. Documentation is always one of those things that everyone wants, as long as someone else does it ;) I happened to know the answer to your question from past experience, but if I had not known the answer, I would have gone to the source code to look (e.g. grepping through the sources for other cases where a SEL_KEYRELEASE message is sent, and seeing how it was handled there). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFAG9ziFXV/hD6oMd0RApg0AKCdVbVgrk4qUVB7nxGSa59oSRxEfACeNVQB 1hBcsfFWFoABFAMNUwr6hAU= =mYb2 -----END PGP SIGNATURE----- |