Well, I really hope I am wrong, but this control seems pretty unusable the way it is implemented right now.
I cannot find a way to get notified immediately when the user commits a selection. The SelectionChangeCommitted, DropDown,
Click, MoseUp/Down events are not implemented. The SelectedIndexChanged event is there but
it does not necessarily mean final selection since the user might just be using the hard buttons to
scroll up and down in the list portion of the ComboBox. Unless I can get notified when the drop down
list gets shown and hidden I cannot be sure what exactly goes on.

So, am I missing something? Is there some way to detect selection immediately after it occurs?

RE: The ComboBox Control by Rob

Rob
Mon Mar 27 06:20:03 CST 2006

In your scenario, the only way you can guarantee the user has finished
selection is by using the LostFocus event. I'm not sure you can place all of
the blame on the combobox since you are able to use the scroll bar to scroll
the list, or jump to a letter using the keyboard (without causing a
selection) rather than cycle through the list using a mouse or arrow key.

Here's another odd behavior involving the combobox and the new pda/phone
device with slideout keyboard. In some instances, sliding out the keyboard
and making the screen landscape and causing a scrollbar to appear, a combobox
at the bottom causes the screen to jump back to the top of the form so that
you cannot select anything. I have had to replace a couple of combo boxes
with listboxes to avoid this.

"Tsviatko Yovtchev" wrote:

> Well, I really hope I am wrong, but this control seems pretty unusable the way it is implemented right now.
> I cannot find a way to get notified immediately when the user commits a selection. The SelectionChangeCommitted, DropDown,
> Click, MoseUp/Down events are not implemented. The SelectedIndexChanged event is there but
> it does not necessarily mean final selection since the user might just be using the hard buttons to
> scroll up and down in the list portion of the ComboBox. Unless I can get notified when the drop down
> list gets shown and hidden I cannot be sure what exactly goes on.
>
> So, am I missing something? Is there some way to detect selection immediately after it occurs?
>

Re: The ComboBox Control by Martin

Martin
Mon Mar 27 13:13:14 CST 2006

This is a multi-part message in MIME format.

------=_NextPart_000_0030_01C651F4.074EE980
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

hi,
if you need "DropDown" event I see one in ComboBox control developed by =
the Labit,
there are some controls with extended set of events in their VDS suite
http://www.labitweb.com

"Rob" <Rob@discussions.microsoft.com> wrote in message =
news:677B66C6-D101-43CA-9301-642D8A3E57B3@microsoft.com...
In your scenario, the only way you can guarantee the user has finished =

selection is by using the LostFocus event. I'm not sure you can place =
all of=20
the blame on the combobox since you are able to use the scroll bar to =
scroll=20
the list, or jump to a letter using the keyboard (without causing a=20
selection) rather than cycle through the list using a mouse or arrow =
key. =20

Here's another odd behavior involving the combobox and the new =
pda/phone=20
device with slideout keyboard. In some instances, sliding out the =
keyboard=20
and making the screen landscape and causing a scrollbar to appear, a =
combobox=20
at the bottom causes the screen to jump back to the top of the form so =
that=20
you cannot select anything. I have had to replace a couple of combo =
boxes=20
with listboxes to avoid this.

"Tsviatko Yovtchev" wrote:

> Well, I really hope I am wrong, but this control seems pretty =
unusable the way it is implemented right now.
> I cannot find a way to get notified immediately when the user =
commits a selection. The SelectionChangeCommitted, DropDown,
> Click, MoseUp/Down events are not implemented. The =
SelectedIndexChanged event is there but
> it does not necessarily mean final selection since the user might =
just be using the hard buttons to
> scroll up and down in the list portion of the ComboBox. Unless I can =
get notified when the drop down
> list gets shown and hidden I cannot be sure what exactly goes on.
>=20
> So, am I missing something? Is there some way to detect selection =
immediately after it occurs?
>
------=_NextPart_000_0030_01C651F4.074EE980
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.3790.2577" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>if you need "<FONT face=3D"Times New =
Roman"=20
size=3D3>DropDown" event I see one in ComboBox control developed by the=20
Labit,</FONT></FONT></DIV>
<DIV>there are some controls with extended set of events in their VDS=20
suite</DIV>
<DIV><A =
href=3D"http://www.labitweb.com">http://www.labitweb.com</A></DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Rob" &lt;<A=20
=
href=3D"mailto:Rob@discussions.microsoft.com">Rob@discussions.microsoft.c=
om</A>&gt;=20
wrote in message <A=20
=
href=3D"news:677B66C6-D101-43CA-9301-642D8A3E57B3@microsoft.com">news:677=
B66C6-D101-43CA-9301-642D8A3E57B3@microsoft.com</A>...</DIV>In=20
your scenario, the only way you can guarantee the user has finished=20
<BR>selection is by using the LostFocus event.&nbsp; I'm not sure you =
can=20
place all of <BR>the blame on the combobox since you are able to use =
the=20
scroll bar to scroll <BR>the list, or jump to a letter using the =
keyboard=20
(without causing a <BR>selection) rather than cycle through the list =
using a=20
mouse or arrow key.&nbsp; <BR><BR>Here's another odd behavior =
involving the=20
combobox and the new pda/phone <BR>device with slideout =
keyboard.&nbsp; In=20
some instances, sliding out the keyboard <BR>and making the screen =
landscape=20
and causing a scrollbar to appear, a combobox <BR>at the bottom causes =
the=20
screen to jump back to the top of the form so that <BR>you cannot =
select=20
anything.&nbsp; I have had to replace a couple of combo boxes <BR>with =

listboxes to avoid this.<BR><BR>"Tsviatko Yovtchev" wrote:<BR><BR>&gt; =
Well, I=20
really hope I am wrong, but this control seems pretty unusable the way =
it is=20
implemented right now.<BR>&gt; I cannot find a way to get notified =
immediately=20
when the user commits a selection. The SelectionChangeCommitted,=20
DropDown,<BR>&gt; Click, MoseUp/Down events are not implemented. The=20
SelectedIndexChanged event is there but<BR>&gt; it does not =
necessarily mean=20
final selection since the user might just be using the hard buttons =
to<BR>&gt;=20
scroll up and down in the list portion of the ComboBox. Unless I can =
get=20
notified when the drop down<BR>&gt; list gets shown and hidden I =
cannot be=20
sure what exactly goes on.<BR>&gt; <BR>&gt; So, am I missing =
something? Is=20
there some way to detect selection immediately after it=20
occurs?<BR>&gt;</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0030_01C651F4.074EE980--