BTW, Istvan, do I recall that you may have fixed FLsetVal_i to work with
FLbutBank? (The latter always defaulted to an initial 0 selection rather
than anything you might have tried to select through FLsetVal_i.)

I believe the same problem was reflected in FLbutton as well, for it is/was
impossible to set the button's initial state (through FLsetVal_i) to on
(1) - only off (0).

Art Hunkins

----- Original Message -----
From: "Istvan Varga" 
To: 
Sent: Tuesday, February 14, 2006 3:48 PM
Subject: Re: [Csnd] FLsetVal


> On Tuesday 14 February 2006 21:04, Ben McAllister wrote:
>
> > Devs - are there any other widgets besides FLbutton and FLbutBank
> > which FLSetval will not support?
>
> FLsetVal (the k-rate version) supports widgets derived from Fl_Valuator,
> that is:
>
>   Fl_Adjuster
>   Fl_Counter
>   Fl_Dial
>   Fl_Roller
>   Fl_Slider
>   Fl_Value_Input
>   Fl_Value_Output
>
> These are FLTK class names, and not opcodes, but it should be easy to find
> out the corresponding opcodes. Fl_Dial is used by FLknob.
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

I view this change as a significant improvement and as such you have my 
humble thanks, Istvan.


-David

On Feb 15, 2006, at 1:25 PM, Istvan Varga wrote:

> The CVS sources have been changed so that now both FLsetVal and 
> FLsetVal_i
> can be used with buttons and button banks. In the case of FLbutton, the
> value should be either 'ion' or 'ioff' as specified for FLbutton, 
> otherwise
> the call to FLsetVal or FLsetVal_i is ignored. For FLbutBank, the value
> should be an integer in the range 0 to (number_of_buttons - 1), 
> otherwise
> it is ignored.
>
> On Wednesday 15 February 2006 01:33, Art Hunkins wrote:
>
>> BTW, Istvan, do I recall that you may have fixed FLsetVal_i to work 
>> with
>> FLbutBank? (The latter always defaulted to an initial 0 selection 
>> rather
>> than anything you might have tried to select through FLsetVal_i.)
>>
>> I believe the same problem was reflected in FLbutton as well, for it 
>> is/was
>> impossible to set the button's initial state (through FLsetVal_i) to 
>> on
>> (1) - only off (0).