FLTK widgets don't work within Rory Walsh's Lettuce front end either.

Since I work in real time, a visual performance interface is very important.

As a result of the FLTK issues, I've done the following:
1) for a performance interface in Windows only, I use Lettuce's widgets 
(another sort) in standalone exec's. (Rory promises that these exec's will 
be cross-platform "soon.")
2) for cross-platform compatibility, no widgets at all; command line only, 
with all performer setup options (for which widgets would otherwise be used) 
being put in orchestra macros and edited there as necessary.

Another reason for abandoning FLTK was that it had issues with MacCsound, 
which was (and is still, I believe) the preferred version (front end?) for 
Mac users. I'm not aware whether or not the issues with MacCsound and FLTK 
were ever resolved. A contributing factor was that MacCsound had its own 
unique system of widgets!

Art Hunkins

----- Original Message ----- 
From: "victor" 
To: 
Sent: Thursday, June 05, 2008 4:00 PM
Subject: [Csnd] Re: Re: FLTK Widgets Not Working (Windows)


> There is an outstanding issue with FLTK that seems to prevent
> on Windows to run the widgets from a FLTK host (ie. Csound5GUI)
> at least on my windows build.
> It also seems to prevent the virtual midi keyboard to work with
> widgets. The FLTK widget code is so horrid that I feel relatively
> unmotivated to do something about it.
>
> However, widgets work fine from the command-line, on their
> own.
>
> Victor
>
>
> ----- Original Message ----- 
> From: "Michael Gogins" 
> To: 
> Sent: Thursday, June 05, 2008 8:20 PM
> Subject: [Csnd] Re: FLTK Widgets Not Working (Windows)
>
>
>>I myself do not use the FLTK opcodes. I prefer to write Python 
>>applications that communicate with Csound through the Python Csound API.
>>
>> However, when I HAVE on occasion used the FLTK opcodes, I only recall 
>> them working when I used the command-line version of Csound.
>>
>> Hope this helps,
>> Mike
>>
>> -----Original Message-----
>>>From: Jim Aikin 
>>>Sent: Jun 5, 2008 3:07 PM
>>>To: csound@lists.bath.ac.uk
>>>Subject: [Csnd]  FLTK Widgets Not Working (Windows)
>>>
>>>
>>>When I load the second block of code given in the manual's "FLTK Widgets 
>>>and
>>>GUI controllers" page (the one that instantiates two panels and puts a
>>>slider in each of them) and then run it from Csound5gui in Windows, the 
>>>FLTK
>>>windows are drawn to the screen, but the client area isn't. The client 
>>>area
>>>still holds whatever was on the screen before the window was drawn. There 
>>>is
>>>no visible slider.
>>>
>>>I've tried this in two computers. One has an openGL-compatible graphics
>>>card, the other doesn't. The performance is not identical; without 
>>>openGL,
>>>there are some additional redraw problems when a window is dragged. But 
>>>even
>>>with openGL, the code simply doesn't work as given.
>>>
>>>To save everyone the trouble of looking it up, the code is given below. 
>>>Is
>>>there something easily fixable here? Thanks!
>>>
>>>--Jim Aikin
>>>
>>>;*************************************************
>>>
>>>
>>>
>>>; Select audio/midi flags here according to platform
>>>; Audio out   Audio in    No messages
>>>-odac           -iadc    ; -d     ;;;RT audio I/O
>>>; For Non-realtime ouput leave only the line below:
>>>; -o linseg.wav -W ;;; for file output any platform
>>>
>>>
>>>;*******************************
>>>sr=48000
>>>kr=480
>>>ksmps=100
>>>nchnls=1
>>>
>>>        FLpanel         "Panel1",450,550,100,100 ;***** start of 
>>> container
>>>gk1,iha FLslider        "FLslider 1", 500, 1000, 0 ,1, -1, 300,15, 20,50
>>>        FLpanelEnd      ;***** end of container
>>>
>>>        FLpanel         "Panel2",450,550,100,100 ;***** start of 
>>> container
>>>gk2,ihb FLslider        "FLslider 2", 100, 200, 0 ,1, -1, 300,15, 20,50
>>>        FLpanelEnd      ;***** end of container
>>>
>>>        FLrun           ;***** runs the widget thread, it is always
>>>required!
>>>
>>>instr 1
>>>; gk1 and gk2 variables that contain the output of valuator
>>>; widgets previously defined, can be used inside any instrument
>>>printk2 gk1
>>>printk2 gk2   ;print the values of the valuators whenever they change
>>>endin
>>>;*******************************
>>>
>>>
>>>f 0 3600 ;dummy table for realtime input
>>>e
>>>
>>>
>>>
>>>
>>>-- 
>>>View this message in context: 
>>>http://www.nabble.com/FLTK-Widgets-Not-Working-%28Windows%29-tp17677385p17677385.html
>>>Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>>
>>>Send bugs reports to this list.
>>>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>>>csound"
>>
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

Steven's widgets are very nice, but they are not meant for real-time use.

- Dave

David Akbari wrote:
> You know, I heard Steven Yi's Blue has a widget interface similar to
> the one used in MacCsound where you use the <> syntax for your named
> GUI channels.
> 
> Has anyone compared it to MacCsound, Lettuce, et al ? The fact that
> Blue has the sequencer layout should be a huge signal to Jim to use it
> for his article, since most professional musicians are used to looking
> at something like a sequencer timeline...
> 
> 
> 
> -David