Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link Par2: Windows reserved keys 2000-10-31 -- Ralph Johnston >Has anyone ever had this problem:
>
>I placed keys F1 to F10 on 10 buttons. When the F10 button is disabled and
I press on it, it freezes the use of the 9 other button (F1 to F9).
>
>After some tests, I've noticed that the F10 reacts like the Alt button in that sense
that if I press the 'F' key after having pressed F10, I go to the file menu of my
application. But if I press F10 twice, everything is normal and I can use F1 to F9
as if nothing happened!
This is a less-than-well-documented behavior of Windows. To
paraphrase the Windows Design Book (The Windows Interface: An
Application Design Guide), these are some of the function key
assignments: F1 = Help, F6 = Move to next pane of active window, F8 =
Toggle Extend Mode, if supported, F10 = Toggle menu bar activation.
There are others, like Ctrl-F4 and Alt-F4.
Anyways, what is happening is that your menu bar *is* being activated,
but due to the Win '95 style menu bars, you can't *tell* that they
have been activated. The solution? Don't press F10!
Note, I think that it is Windows that is grabbing the F10 key, not
Clarion, but I'm not totally sure about that.
Today is November 21, 2024, 7:18 am This article has been viewed 35214 times.
|
|