comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Re: CASE a UNAME??

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: CASE a UNAME?? [message #27484 is a reply to message #27483]

Wed, 24 October 2001 21:27

David Fanning
Messages: 11724
Registered: August 2001

Senior Member

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

Report message to a moderator

[Message index]

		Re: CASE a UNAME?? By: Logan Lindquist on Thu, 25 October 2001 07:26
		Re: CASE a UNAME?? By: Logan Lindquist on Thu, 25 October 2001 07:28
		Re: CASE a UNAME?? By: R.Bauer on Thu, 25 October 2001 05:01
		Re: CASE a UNAME?? By: Logan Lindquist on Wed, 24 October 2001 21:29
		Re: CASE a UNAME?? By: Logan Lindquist on Wed, 24 October 2001 21:19
		Re: CASE a UNAME?? By: David Fanning on Wed, 24 October 2001 21:27

Previous Topic:	Single Checkbox with CW_Form?
Next Topic:	Open letter to RSI about dropping Alpha Tru64

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Dec 02 10:46:18 PST 2025

Total time taken to generate the page: 0.08026 seconds