OpenEuphoria

Re: Win32Lib Losing Keys

• Posted by Pete Lomax <petelomax at blueyonder.co.uk> Jul 09, 2004
• 468 views

On Thu, 08 Jul 2004 16:53:05 -0700, Derek Parnell
<guest at RapidEuphoria.com> wrote:

>When we talk about 'focus' we are talking about *keyboard* focus. That is,
<sound of penny dropping>
>which element in the display recieves keyboard events. In the Windows
>paradigm, the only elements that normally get focus are those that keyboard
>activity makes sense for. Now, true, this is a bit arbitary but Microsoft,
<sound of krugerrand dropping>
>and other GUI designs, have decided that in doesn't make sense for the
>parent (background) window to react to keystrokes. So in a nutshell, 
>windows don't get focus but (most other) controls do. 

There are many apps which do not rely on a traditional windows
control. Of course, for me, MEditor springs to mind. Most games, and
indeed Word and Internet Explorer fall into the same category.

>In Win32lib, when a window gets a 'GotFocus' message, I try to locate the
>child control that last had focus for that window and set the new focus to
>that control, rather than the Window itself (and thus no control in that
>window). This is especially relevant when moving between windows.
>
>So I put it to the user base of this library: What do you want to happen
>when a Window gets a 'GotFocus' message?

Perhaps this is the wrong question. Why are we programmers trying to
setFocus(Window)? Is there a more natural way to express the intent,
such as

	create(Hidden,....)
or
	create(Virtual,...)

Regards,
Pete