comp.lang.idl-pvwave archive: archive » Re: State of non-exclusive button

Home » Public Forums » archive » Re: State of non-exclusive button

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

Re: State of non-exclusive button [message #26391 is a reply to message #26390]

Fri, 31 August 2001 11:19

K. Bowman
Messages: 330
Registered: May 2000

Senior Member

In article <MPG.15f96faea752fcf989690@news.frii.com>, David Fanning
<david@dfanning.com> wrote:

> I think you have to keep track of non-exclusive
> buttons the same way you keep track of droplist
> values: you have to have some kind of buttonState
> variable that you store in some user value that is
> easy to get to.

That's what I've been doing, but I thought a widget might be smart
enough to keep track of its own state. ;-)

Ken

Report message to a moderator

[Message index]

		Re: State of non-exclusive button By: R.Bauer on Mon, 03 September 2001 01:11
		Re: State of non-exclusive button By: David Fanning on Fri, 31 August 2001 13:28
		Re: State of non-exclusive button By: Steve Hartmann on Fri, 31 August 2001 11:37
		Re: State of non-exclusive button By: K. Bowman on Fri, 31 August 2001 11:19
		Re: State of non-exclusive button By: David Fanning on Fri, 31 August 2001 09:56

Previous Topic:	better doc_library?
Next Topic:	Could i find some examples for IDL DataMiner ...?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 19:22:47 PDT 2025

Total time taken to generate the page: 0.00449 seconds