Re: Again on kb_event. It almost works
From: L D Blake (not_at_any.adr)
Date: 09/15/04
- Next message: Diane Arons: "Lyle Blake's Pot Business"
- Previous message: Rob Kennedy: "Re: Again on kb_event. It almost works"
- In reply to: Rob Kennedy: "Re: Again on kb_event. It almost works"
- Next in thread: J French: "Re: Again on kb_event. It almost works"
- Reply:(deleted message) J French: "Re: Again on kb_event. It almost works"
- Reply:(deleted message) Rob Kennedy: "Re: Again on kb_event. It almost works"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 14 Sep 2004 18:04:18 -0400
On Tue, 14 Sep 2004 16:48:27 -0500, Rob Kennedy <me3@privacy.net> wrote:
>I think the combo box does capture the mouse (or something like that) by
>itself since it needs to know when the user clicks off the control. I
>can see the same behavior in Microsoft-written programs. Open the
>Windows "Run" dialog. Set focus to the combo box, and place the cursor
>over the edit portion, so it is an I-beam. Press Alt+Down to drop down
>the combo box. Move the mouse anywhere within the bounds of the dialog,
>and it will still be an I-beam. Outside the dialog, the cursor's shape
>appears is normally.
Actually that would be the editor capturing the mouse.
Comboboxes (which I use rather a lot) at winapi level don't generally cause
the mouse cursor to vanish nor do edit windows, which I also use quite a bit.
Frankly, this one's got me stumped.
-----
Laura
- Next message: Diane Arons: "Lyle Blake's Pot Business"
- Previous message: Rob Kennedy: "Re: Again on kb_event. It almost works"
- In reply to: Rob Kennedy: "Re: Again on kb_event. It almost works"
- Next in thread: J French: "Re: Again on kb_event. It almost works"
- Reply:(deleted message) J French: "Re: Again on kb_event. It almost works"
- Reply:(deleted message) Rob Kennedy: "Re: Again on kb_event. It almost works"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|