I have got now a 10.4 machine to play with, so I built csound to
test it. It builds fine and seems to work.

However, the behaviour of the fltk widget opcodes is problematic.
I am getting the problems I experienced when these opcodes were
moved out of csound to a plugin lib.

Effectively, the widgets are not accessible, as the 'revolving wheel'
mouse pointer is active and nothing can be clicked. This happened
on 10.3 at first, but using a dynamic-link fltk lib seemed to resolve
the issue then and I never had any more problems. That was with 1.1.5.

Now in this build I am using v.1.1.6, and I am wondering whether
the problem is with the fltk version or with OSX 10.4

Any suggestions?

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

What happens if you use the -d flag and/or build with noFLTKThreads=1 ?

Victor Lazzarini wrote:
> I have got now a 10.4 machine to play with, so I built csound to
> test it. It builds fine and seems to work.
> 
> However, the behaviour of the fltk widget opcodes is problematic.
> I am getting the problems I experienced when these opcodes were
> moved out of csound to a plugin lib.
> 
> Effectively, the widgets are not accessible, as the 'revolving wheel'
> mouse pointer is active and nothing can be clicked. This happened
> on 10.3 at first, but using a dynamic-link fltk lib seemed to resolve
> the issue then and I never had any more problems. That was with 1.1.5.
> 
> Now in this build I am using v.1.1.6, and I am wondering whether
> the problem is with the fltk version or with OSX 10.4


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Again, does anyone have any idea why I cannot do a "cvs update" on
MacOSX -- it times out -- when the Linux machine on the same local net
can do it every time?  Last time this happened I did a complete
checkout again, but that is tedious, time consuming and does not solve
the issue.
==John ffitch


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'm actually running with -d. Tried the noFLTKThreads (never thought it
was possible to run widgets without thread support). I can actually
click once on a button, but then the revolving wheel comes back, as
if an infinite loop was reached.

The funny thing is that, even though I am linking against
libfltk.dylib, the link appears to be static, because if I rename
the library, the widget plugin library still loads without a problem
(but of course it doesn't work), which seems to indicate that
the FLTK code has been copied into the libwidgets.dylib. Using
-dynamic to force the use of dynamic linking doesn't seem to
work.

I reckon it's again a matter of getting the right linker flags. It would
have been easier if OSX resembled more closely a UNIX system.

Anyway, any suggestions are welcome.

Victor

At 15:11 07/10/2005, you wrote:
>What happens if you use the -d flag and/or build with noFLTKThreads=1 ?
>
>Victor Lazzarini wrote:
>>I have got now a 10.4 machine to play with, so I built csound to
>>test it. It builds fine and seems to work.
>>However, the behaviour of the fltk widget opcodes is problematic.
>>I am getting the problems I experienced when these opcodes were
>>moved out of csound to a plugin lib.
>>Effectively, the widgets are not accessible, as the 'revolving wheel'
>>mouse pointer is active and nothing can be clicked. This happened
>>on 10.3 at first, but using a dynamic-link fltk lib seemed to resolve
>>the issue then and I never had any more problems. That was with 1.1.5.
>>Now in this build I am using v.1.1.6, and I am wondering whether
>>the problem is with the fltk version or with OSX 10.4
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by:
>Power Architecture Resource Center: Free content, downloads, discussions,
>and more. http://solutions.newsforge.com/ibmarch.tmpl
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Forget what I said: libfltk.dylib is only a dynamic link (I grew used to
seeing these in colour and forgot to check). yes the link is dynamic.

Victor


At 17:08 07/10/2005, you wrote:
>I'm actually running with -d. Tried the noFLTKThreads (never thought it
>was possible to run widgets without thread support). I can actually
>click once on a button, but then the revolving wheel comes back, as
>if an infinite loop was reached.
>
>The funny thing is that, even though I am linking against
>libfltk.dylib, the link appears to be static, because if I rename
>the library, the widget plugin library still loads without a problem
>(but of course it doesn't work), which seems to indicate that
>the FLTK code has been copied into the libwidgets.dylib. Using
>-dynamic to force the use of dynamic linking doesn't seem to
>work.
>
>I reckon it's again a matter of getting the right linker flags. It would
>have been easier if OSX resembled more closely a UNIX system.
>
>Anyway, any suggestions are welcome.
>
>Victor
>
>At 15:11 07/10/2005, you wrote:
>>What happens if you use the -d flag and/or build with noFLTKThreads=1 ?
>>
>>Victor Lazzarini wrote:
>>>I have got now a 10.4 machine to play with, so I built csound to
>>>test it. It builds fine and seems to work.
>>>However, the behaviour of the fltk widget opcodes is problematic.
>>>I am getting the problems I experienced when these opcodes were
>>>moved out of csound to a plugin lib.
>>>Effectively, the widgets are not accessible, as the 'revolving wheel'
>>>mouse pointer is active and nothing can be clicked. This happened
>>>on 10.3 at first, but using a dynamic-link fltk lib seemed to resolve
>>>the issue then and I never had any more problems. That was with 1.1.5.
>>>Now in this build I am using v.1.1.6, and I am wondering whether
>>>the problem is with the fltk version or with OSX 10.4
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by:
>>Power Architecture Resource Center: Free content, downloads, discussions,
>>and more. http://solutions.newsforge.com/ibmarch.tmpl
>>_______________________________________________
>>Csound-devel mailing list
>>Csound-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>Victor Lazzarini
>Music Technology Laboratory
>Music Department
>National University of Ireland, Maynooth
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by:
>Power Architecture Resource Center: Free content, downloads, discussions,
>and more. http://solutions.newsforge.com/ibmarch.tmpl
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I tried a 1.1.5 FLTK dylib with widgets.dylib set to no threads and
it works. It doesn't work against a threading version of widgets.dylib.
Strange, as in 10.3.9 it works with threads.

The 1.1.5 I used was built on 10.2 (or 10.3, I'm not sure). So that might
be why the thread version does not work. I have to build it again on
10.4 to see if there is any difference.

In any case, at least for the Macs 1.1.5 is the version that should be
used. Forget 1.1.6 (I haven't tested 1.2 or 2.0).

All these things have to be considered when thinking of a release
candidate. I have an impression that if widgets.cpp was linked
statically into csound, we would avoid a lot of trouble.

Victor

At 17:08 07/10/2005, you wrote:
>I'm actually running with -d. Tried the noFLTKThreads (never thought it
>was possible to run widgets without thread support). I can actually
>click once on a button, but then the revolving wheel comes back, as
>if an infinite loop was reached.
>
>The funny thing is that, even though I am linking against
>libfltk.dylib, the link appears to be static, because if I rename
>the library, the widget plugin library still loads without a problem
>(but of course it doesn't work), which seems to indicate that
>the FLTK code has been copied into the libwidgets.dylib. Using
>-dynamic to force the use of dynamic linking doesn't seem to
>work.
>
>I reckon it's again a matter of getting the right linker flags. It would
>have been easier if OSX resembled more closely a UNIX system.
>
>Anyway, any suggestions are welcome.
>
>Victor
>
>At 15:11 07/10/2005, you wrote:
>>What happens if you use the -d flag and/or build with noFLTKThreads=1 ?
>>
>>Victor Lazzarini wrote:
>>>I have got now a 10.4 machine to play with, so I built csound to
>>>test it. It builds fine and seems to work.
>>>However, the behaviour of the fltk widget opcodes is problematic.
>>>I am getting the problems I experienced when these opcodes were
>>>moved out of csound to a plugin lib.
>>>Effectively, the widgets are not accessible, as the 'revolving wheel'
>>>mouse pointer is active and nothing can be clicked. This happened
>>>on 10.3 at first, but using a dynamic-link fltk lib seemed to resolve
>>>the issue then and I never had any more problems. That was with 1.1.5.
>>>Now in this build I am using v.1.1.6, and I am wondering whether
>>>the problem is with the fltk version or with OSX 10.4
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by:
>>Power Architecture Resource Center: Free content, downloads, discussions,
>>and more. http://solutions.newsforge.com/ibmarch.tmpl
>>_______________________________________________
>>Csound-devel mailing list
>>Csound-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>Victor Lazzarini
>Music Technology Laboratory
>Music Department
>National University of Ireland, Maynooth
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by:
>Power Architecture Resource Center: Free content, downloads, discussions,
>and more. http://solutions.newsforge.com/ibmarch.tmpl
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I seemed to be able to get 1.1.6 working. The trouble was that
I was compiling as usual with gcc3opt and the lib I build was
with the default compiler (4 I expect). Csound was being built
with 3 and fltk with 4. I never realised that there was actually
a difference between gcc3opt and gcc4opt, but it appears to
exist (I didn't check SConstruct).

But it needs to be built with no threads. What is the actual difference?
I thought the widgets had to run in a separate thread. Does it mean
that they are running in the same thread as the csound engine?

The threading option works with gcc3 on 10.3

Victor


Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Victor Lazzarini wrote:

> I seemed to be able to get 1.1.6 working. The trouble was that
> I was compiling as usual with gcc3opt and the lib I build was
> with the default compiler (4 I expect). Csound was being built
> with 3 and fltk with 4. I never realised that there was actually
> a difference between gcc3opt and gcc4opt, but it appears to
> exist (I didn't check SConstruct).

Well, then probably you need to compile Csound with GCC 4 (use the
CC, CXX, and LINK scons options to select the C compiler, C++ compiler,
and linker). gcc3opt or gcc4opt do not select a particular compiler,
the only difference is the use of an additional optimization flag
by gcc4opt that I so far found to be useless.

> But it needs to be built with no threads. What is the actual difference?
> I thought the widgets had to run in a separate thread. Does it mean
> that they are running in the same thread as the csound engine?

Yes, when built with noFLTKThreads=1, the FLTK GUI runs in the
audio thread (it still uses Fl::lock() and Fl::unlock(), though,
but those may not actually be needed, and could be #ifdef'd out
for noFLTKThreads=1). This may improve reliability at the expense
of performance. Quitting by closing the FLTK windows does not
work in this case, though, so you need to use ^C.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Victor,

I had been having trouble recently as well trying to set up Csound5 on 
Dr. Boulanger's 10.4 machine.

We tried FLTK versions 1.1.4, 1.1.5, and 1.1.6 on Mac OSX Tiger.

We were only able to get 1.1.4 to work (launch) but often times we 
would see the FLTK interface loads correctly but is unresponsive... 
even with -d. I tried using the "Spin Control" app that comes in the 
OSX developer's kit and it shows the FLTK thread is running an infinite 
loop, but it cannot isolate the symbol that is causing it.

We were never able to get it properly working... Personally I still use 
OS 10.3.9 and FLTK works wonderfully. There is a problem still in 
loading an FLpanel and GEN displays simultaneously that can usually be 
avoided by using the -d flag.

Also, I still have a "stable build" from May 16 2005 in addition to a 
current CVS build. Although the current CVS's API is far superior to 
the May 16 build, the May 16 build can still load working FLTK 1.1.6 
and GEN displays simultaneously.

If I remember correctly, May 16 was shortly before moving the 
libwidgets from a static to a dynamically loaded module.


-David

On Oct 7, 2005, at 1:16 PM, Victor Lazzarini wrote:

> I seemed to be able to get 1.1.6 working. The trouble was that
> I was compiling as usual with gcc3opt and the lib I build was
> with the default compiler (4 I expect). Csound was being built
> with 3 and fltk with 4. I never realised that there was actually
> a difference between gcc3opt and gcc4opt, but it appears to
> exist (I didn't check SConstruct).
>
> But it needs to be built with no threads. What is the actual 
> difference?
> I thought the widgets had to run in a separate thread. Does it mean
> that they are running in the same thread as the csound engine?
>
> The threading option works with gcc3 on 10.3
>
> Victor



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net