I have a list popup on a form that is triggered by a button push.
I use: 

selectP = LstGetSelectionText(listP, LstPopupList(listP);

I then test selectP for NULL and if not NULL then I process the list
selection. I want the processing of selected list to be as usual when a
list item is selected.

However, when a selection is made outside the bounds of the list
(selectP == NULL) I take a different path.  I would like whatever button
is pressed to be immediately processed. Right now, that press just
closes the list and I have to again  tap the button.  

So, say I have the list displayed with the statement above and I press
MyOtherButton.  Right now the list just closes with a beep.  I would
like the application to close the list as it does now but also envoke
the handler for MyOtherButton.

I know this is the normal way this works.  But since I can execute
one of two routines right after the selections is made, it seems
that there might be a way to queue up an event or something that will
allow the event handler for MyOtherButton.  I also know I can just queue
up whatever I want for a particular handler but I don't know which
button will be pressed at compile time, so this must work for any button
that is pressed.

Are there any creative people out there who know how to do this this?

Thanks

----------------------------------------------------
Shoot-to-Win

Protect the 2nd Amendment
----------------------------------------------------

Reply via email to