Yeah - I realize that the listbox passes its events to the parent
window. But both the container control as well as the listbox are
children of their parent window.
Why would a keydown event get passed to another child?
On Mar 25, 2006, at 11:43 AM, Michael Rebar wrote:
On 3/25/06 7:29 AM, "Björn Eiríksson" <[EMAIL PROTECTED]> wrote:
On 25.3.2006, at 14:56, Jay Wooten wrote:
Say you have a window with a listbox and a few rows of data
in that same window you have a container control (an empty one will
work)
When you select a row in the listbox, and then press a key - like
delete, why does the container control get the keydown event?
To test this, put a msgbox in the keydown event of the container
control.
Is this correct behavior?
REALbasic usually passes KeyDown events to the Parent control/Window
if you do not return true from the KeyDown event of the Child control
(in this case the ListBox)
I think Jay's point is that the ListBox is not a child control of the
container.
No, IMO it is not correct behavior.
Michael
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
