> 1) Hopefully the exe could be made to exit with only Escape or CTRL+C.
> Requiring a button implementing an event "e" code would mean rewriting
> .csd's especially for this purpose. I've many of them (over 100 by now), and
> would not want to undertake such a project.

Hopefully, although if I can't figure out why fltk keeps crashing 
Lettuce on a second run we can forget about that!

> 2) I presume that the  issue already discussed would be treated
> here in the same way (of necessity) - though in this instance it would
> definitely be more of an inconvenience for the user.

Again, it depends on if/when I get fltk running without any problems 
from Lettuce.

> 3) Would this exe, and for that matter others (non-FLTK) from Lettuce,
> necessarily need to be run in the presence of Lettuce? (I presume and hope
> not.)

No, they don't need to be now either. That's the idea. You can build an 
exe and then distribute just the exe to anyone you want, you don't have 
to send csd files or anything, when you 'compile' the exe's Lettuce 
embeds the csd file into the exe.

> 4) How would the directory locations be handled for the standalone FLTK exe?
> Will the environmental variables from the Csound installation suffice?
> (Given the path command, I also assume the FLTK exe can be run from
> anywhere.)

They should do. Again all this depends on me getting the fltk opcodes to 
run in Lettuce without a crash. I've asked about this on the developers 
list so hopefully someone there will come to my aid! CAN YOU HEAR ME 
DEVELOPERS!!!!

Rory.

Rory,

Regarding the above, several comments/questions:

1) Hopefully the exe could be made to exit with only Escape or CTRL+C.
Requiring a button implementing an event "e" code would mean rewriting
.csd's especially for this purpose. I've many of them (over 100 by now), and
would not want to undertake such a project.

2) I presume that the  issue already discussed would be treated
here in the same way (of necessity) - though in this instance it would
definitely be more of an inconvenience for the user.

3) Would this exe, and for that matter others (non-FLTK) from Lettuce,
necessarily need to be run in the presence of Lettuce? (I presume and hope
not.)

4) How would the directory locations be handled for the standalone FLTK exe?
Will the environmental variables from the Csound installation suffice?
(Given the path command, I also assume the FLTK exe can be run from
anywhere.)

Art Hunkins

Rory Walsh wrote:

> They should do. Again all this depends on me getting the fltk opcodes 
> to run in Lettuce without a crash. I've asked about this on the 
> developers list so hopefully someone there will come to my aid! CAN 
> YOU HEAR ME DEVELOPERS!!!!

Shouting at them is probably not the best way to ensure their 
participation. And they are very busy people too.

Rory, the FLTK stuff has always had threading issues. If you understand 
the way threads work you can start debugging your software. IIRC you're 
developing on Windows, yes ? What debugger do you use there ? Have you 
done a backtrace to determine where the code poops out ?

Btw, I ran Lettuce under WINE, using the recommended Cs5. Everything 
appears to load all right but I haven't tested anything with it. Looks 
nice, the breakpoint editor is very well-conceived.

Good work, I encourage you to produce a native Linux version.

Best,

dp

> Shouting at them is probably not the best way to ensure their 
> participation. And they are very busy people too.

I was just kidding. I realise how busy they are, and believe if it had 
not been for their help Lettuce would still be just an idea. the first 
strange thing and probably the root to my problem is that when I stop 
Csound from Lettuce the fltk panel remains open, hence when I re-run the 
instrument it's not surprising that I get errors. I'm working with the 
Borland C++ debugger. I'd like to know more about the threading issues 
with the fltk opcodes. Are there any preprocessor commands I can include 
that may sort it out?

> Rory, the FLTK stuff has always had threading issues. If you understand 
> the way threads work you can start debugging your software. IIRC you're 
> developing on Windows, yes ? What debugger do you use there ? Have you 
> done a backtrace to determine where the code poops out ?
> 
> Btw, I ran Lettuce under WINE, using the recommended Cs5. Everything 
> appears to load all right but I haven't tested anything with it. Looks 
> nice, the breakpoint editor is very well-conceived.
> 
> Good work, I encourage you to produce a native Linux version.
> 
> Best,
> 
> dp
> 

David Akbari wrote:

> On 5/1/06, Dave Phillips  wrote:
>
>> Btw, I ran Lettuce under WINE, using the recommended Cs5.
>
>
> Could you share you secret on how you got it to run with WINE on Linux ?
>
> I successfully ran and installed the Lettuce1-3-2.exe and the
> Csound5.02-win32-f.exe files with WINE but when I try to run Lettuce I
> get this error :

Hi David:

  I haven't tested Rory's latest version, I'll give it a whirl and let 
you know how it turns out.

  I did nothing special except update WINE to 0.9.11. I'm running Debian 
Etch here, btw, from Demudi 1.3. Note that I haven't tested anything 
with Lettuce yet, I merely installed and ran it. Ditto with the Cs5 
version Rory points to on the Lettuce page.

  What version of WINE are you using ?

Best,

dp

On May 1, 2006, at 4:37 PM, Dave Phillips wrote:

>  What version of WINE are you using ?

running wine --version returns
"Wine 0.9"

so I should probably update! I'm running the 2.6.14-kanotix-9 kernel.


-David

David Akbari wrote:

>
> On May 1, 2006, at 4:37 PM, Dave Phillips wrote:
>
>>  What version of WINE are you using ?
>
>
> running wine --version returns
> "Wine 0.9"
>
> so I should probably update! I'm running the 2.6.14-kanotix-9 kernel.

David, I just opened Lettuce 1.3.2 under WINE. I also tried running a 
test file, it didn't work but I think I'm just missing some settings. 
Ditto with CsoundAV, I opened it but haven't tested it.

Best,

dp

Rory Walsh wrote:

> ... probably the root to my problem is that when I stop Csound from 
> Lettuce the fltk panel remains open, hence when I re-run the 
> instrument it's not surprising that I get errors. I'm working with the 
> Borland C++ debugger. I'd like to know more about the threading issues 
> with the fltk opcodes. Are there any preprocessor commands I can 
> include that may sort it out?

Alas, I'm too far from Windows these days, but perhaps I can offer a 
hint. You'll need a debugger capable of illustrating the separate 
threads so you can see where/why the FLTK panel stays open. Maybe 
there's a setting for the Borland debugger ?

Can you run the executable from the debugger ? If so, run a backtrace 
from the error point and post the results. Istvan and Michael can 
certainly help you more than I can. I am not a programmer, and C++ 
really leaves me in the dust. :)

Best,

dp

Thanks Dave. I will keep looking into it, the answer may just hit me 
sooner or later! Thanks for your help.

Rory.

Dave Phillips wrote:
> Rory Walsh wrote:
> 
>> ... probably the root to my problem is that when I stop Csound from 
>> Lettuce the fltk panel remains open, hence when I re-run the 
>> instrument it's not surprising that I get errors. I'm working with the 
>> Borland C++ debugger. I'd like to know more about the threading issues 
>> with the fltk opcodes. Are there any preprocessor commands I can 
>> include that may sort it out?
> 
> Alas, I'm too far from Windows these days, but perhaps I can offer a 
> hint. You'll need a debugger capable of illustrating the separate 
> threads so you can see where/why the FLTK panel stays open. Maybe 
> there's a setting for the Borland debugger ?
> 
> Can you run the executable from the debugger ? If so, run a backtrace 
> from the error point and post the results. Istvan and Michael can 
> certainly help you more than I can. I am not a programmer, and C++ 
> really leaves me in the dust. :)
> 
> Best,
> 
> dp
>