Victor,

Did I understand you to say that these FLTK issues have now been remedied in
your new Csound5 pre-release materials for the Mac OS?

Or, as Dave suggests, do we ultimately need to look beyond FLTK for graphics
that work across all platforms?

Personally, my "graphical needs" are fairly simple, and for now, FLTK
widgets service them well.

Art Hunkins

----- Original Message -----
From: "David Akbari" 
To: 
Sent: Friday, December 30, 2005 2:07 AM
Subject: Re: [Csnd] [Cs-dev] fl graphics on mac + rtaudio


> Hi Art, others,
>
> To achieve compatibility between Mac OS and Windows/Linux for
> compositions, I have found it quite effective to create abstractions of
> concepts such as UDO's (for a log slider for example) then use a
> generic, linear control slider in any arbitrary frontend/wrapper/UI.
>
> I use csoundapi~ for Pd on both PC and Mac and I've found the
> invalue/outvalue mechanism to be quite useful, however the best seems
> to be to use UDOs - especially when using Csound5's interapplication
> communication protocol OSC implementation, for example. You then no
> longer require any sort of FLsetVal in your orc and it seems to make
> things generally cleaner.
>
> I tried to develop a realtime system for Dr. Boulanger to use with the
> p5 glove at the Sounds Electric '05 conference and I seemed to run into
> several problems with the FLTK implementation in Csound5 - so much that
> I simply dropped the GUI and just make a standalone Csound file that
> printed the necessary information to the standard output :)
>
> Some of the problems could have been related to the fact that I was
> using a version of Csound5 compiled on Mac OS 10.3 with noFLTKthreads=0
> and Dr. Boulanger was using a version of Csound5 on Mac OS 10.4 with
> noFLTKthreads=1. The oddities were so strange .... one such oddity was
> the fact that the sliders were all reversed!
>
> In general, it seems that the invalue/outvalue implementation seems to
> be quite transparent between MacCsound, csoundapi~ and the new
> TclCsound, although I prefer to use UDO's in my compositions to
> facilitate maximum transparency between Mac, Windows, and Linux (I use
> all 3 regularly and I cannot waste time with implementation details).
>
> TclCsound is the FLTK of the future, IMHO.
>
> Peace be with you all during this holiday season!
>
>
> -David
>
> On Dec 29, 2005, at 11:36 AM, Art Hunkins wrote:
>
> > I'd be interested in hearing of any composers on the Mac OS's who
> > routinely
> > use FLTK widgets. (I assume that until recently FLTK didn't work on the
> > Mac.)
> >
> > To be sure that my works *can* be performed by others - on many
> > devices,
> > I've collected (and continue to collect) a large number of such  -
> > currently
> > 20 or more. (I also document my works extensively via an instructional
> > text
> > file.) Only two or three devices are keyboards. (None of my pieces
> > require a
> > keyboard, although at least one is performable on such.) eBay has been
> > invaluable in this "controller search".
> >
> > I may well do an article on "tips for writing for a wide variety of
> > control
> > surfaces," including a segment on "what to look for in a control
> > surface."
> > The only thing keeping me from it is the feeling that my experience
> > may be
> > much too personal, and that there's absolutely no substitute for user
> > experience in this area.
> >
> > Art Hunkins
>
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk