SelectionChangeCommitted event

[SH]

Why doesn't the SelectionChange Committed event fire when the user
chooses an item via the keyboard and then presses the return key or the
tab key?

I have a combobox with AutoCompleteSou rce=ListItems and
AutoCompleteMod e=SuggestAppend . When the user makes a selection via the
mouse, the SelectionChange Committed event fires. Good. But when they
make a selection via the keyboard and press the return key or the tab
key to commit their choise, the SelectionChange Committed doesn't fire.
Why? Aren't they valid commitment methods?

[vbnetdev]

Re: SelectionChange Committed event

AddHandler ColumnComboBox. SelectionChange Committed, AddressOf
ComboStartEditi ng

Next, build your procedure in an Overrides Region:

Private Sub ComboStartEditi ng(ByVal sender As Object, ByVal e As EventArgs)

blnStartEditing = True
MyBase.ColumnSt artedEditing(se nder)
...blah, blah, blah
End Sub

--
Get a powerful web, database, application, and email hosting with KJM
Solutions

http://www.kjmsolutions.com

"SH" <shamada@prupip e.com> wrote in message
news:_So5g.122$ F4.102@newsread 1.news.pas.eart hlink.net...[color=blue]
> Why doesn't the SelectionChange Committed event fire when the user chooses
> an item via the keyboard and then presses the return key or the tab key?
>
> I have a combobox with AutoCompleteSou rce=ListItems and
> AutoCompleteMod e=SuggestAppend . When the user makes a selection via the
> mouse, the SelectionChange Committed event fires. Good. But when they make
> a selection via the keyboard and press the return key or the tab key to
> commit their choise, the SelectionChange Committed doesn't fire. Why?
> Aren't they valid commitment methods?[/color]

[sh]

Re: SelectionChange Committed event

Thanks for your response.

But isn't that just getting around the problem. Am I wrong in assuming
that the return key and tab key SHOULD fire the SelectionChange Committed
event?

vbnetdev wrote:[color=blue]
> AddHandler ColumnComboBox. SelectionChange Committed, AddressOf
> ComboStartEditi ng
>
> Next, build your procedure in an Overrides Region:
>
> Private Sub ComboStartEditi ng(ByVal sender As Object, ByVal e As EventArgs)
>
> blnStartEditing = True
> MyBase.ColumnSt artedEditing(se nder)
> ...blah, blah, blah
> End Sub
>[/color]

[vbnetdev]

Re: SelectionChange Committed event

Its a solution. I try not to worry about it if it works. No time in a
production environment to worry about such things.

--
Get a powerful web, database, application, and email hosting with KJM
Solutions

http://www.kjmsolutions.com

"sh" <shamada@prupip e.com> wrote in message
news:6Ir5g.5774 $An2.1124@newsr ead2.news.pas.e arthlink.net...[color=blue]
> Thanks for your response.
>
> But isn't that just getting around the problem. Am I wrong in assuming
> that the return key and tab key SHOULD fire the SelectionChange Committed
> event?
>
> vbnetdev wrote:[color=green]
>> AddHandler ColumnComboBox. SelectionChange Committed, AddressOf
>> ComboStartEditi ng
>>
>> Next, build your procedure in an Overrides Region:
>>
>> Private Sub ComboStartEditi ng(ByVal sender As Object, ByVal e As
>> EventArgs)
>>
>> blnStartEditing = True
>> MyBase.ColumnSt artedEditing(se nder)
>> ...blah, blah, blah
>> End Sub
>>[/color][/color]