comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: CASE a UNAME??
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: CASE a UNAME?? [message #27474] Thu, 25 October 2001 07:26 Go to previous message
Logan Lindquist is currently offline  Logan Lindquist
Messages: 50
Registered: October 2001
Member
David,
Thanks Again for the Help!
Logan

"David Fanning" <david@dfanning.com> wrote in message
news:MPG.164142b35a4bfde3989723@news.frii.com...
> Logan Lindquist (llindqusit@mrdoc.cc) writes:
>
>> I would like my program to do a CASE statement in an
>> event handler procedure that is the same for two different
>> options in the menu of my program. Say I want to change
>> the window size by selecting a different option in my
>> menu. By doing a CASE statement on the UNAME of the
>> different options I can figure out which option created
>> the event? So I guess the Question of the hour is:
>> What is the best way to find which Widget_Button
>> created an event in a general event handler procedure
>> called by several such Widget_Button's?
>
> I typically look at the button's value.
>
> Widget_Control, event.id, Get_Value=buttonValue
> CASE buttonValue OF
>
> Just be sure you spell this in your case statement
> *exactly* the way you spelled it on the button!
>
> Cheers,
>
> David
>
> --
> David W. Fanning, Ph.D.
> Fanning Software Consulting
> Phone: 970-221-0438, E-mail: david@dfanning.com
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
> Toll-Free IDL Book Orders: 1-888-461-0155
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Single Checkbox with CW_Form?
Next Topic: Open letter to RSI about dropping Alpha Tru64

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 13:50:16 PDT 2025

Total time taken to generate the page: 1.04129 seconds