QuteCsound is awesome.
I have exactly one inquiry.
It's what almost always keeps me from IDEs.
Are there any plans for/is there a chance that QuteCsound will get  
some sort of preset, modifiable editing modes built-in?
Am I totally missing the part where I can do this painlessly already  
and I am looking in the wrong place?

I'm missing vi navigation and shortcuts, and I'm sure some folks  
would like to use their emacs or what-have-you shortcuts.
I know this is a young frontend, and it's not a gripe.
I am learning to hate myself when I start craving features.
(cue conversation about limited tools and art and so on)

Also . . .
why is FLTK "unsafe?" Everything I've tried seemed to run fine. I  
tried one example that needed MIDI input without MIDI input and the  
app didn't crash, it just took me back to the main window.

Greg


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On OSX, FLTK grabs the menus and don't return them. Better to run FLTK  
CSDs as a separate process ('run in term')

Victor

On 16 Apr 2010, at 14:32, gmschroeder wrote:

>
> Also . . .
> why is FLTK "unsafe?" Everything I've tried seemed to run fine. I  
> tried one example that needed MIDI input without MIDI input and the  
> app didn't crash, it just took me back to the main window.
>
> Greg



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi,

You can set the shortcuts in the Edit->Set Keyboard shortcuts window.
Not as powerful as Emacs/Vim modes, but maybe a start?

The "unsafe" part was due to threading issues in QuteCsound, which
caused instability with FLTK. Maybe they have been solved over time
with improvements in QuteCsound? I rarely use FLTK so I can't be
sure...

Cheers,
Andrés

On Fri, Apr 16, 2010 at 2:32 PM, gmschroeder  wrote:
> QuteCsound is awesome.
> I have exactly one inquiry.
> It's what almost always keeps me from IDEs.
> Are there any plans for/is there a chance that QuteCsound will get some sort
> of preset, modifiable editing modes built-in?
> Am I totally missing the part where I can do this painlessly already and I
> am looking in the wrong place?
>
> I'm missing vi navigation and shortcuts, and I'm sure some folks would like
> to use their emacs or what-have-you shortcuts.
> I know this is a young frontend, and it's not a gripe.
> I am learning to hate myself when I start craving features.
> (cue conversation about limited tools and art and so on)
>
> Also . . .
> why is FLTK "unsafe?" Everything I've tried seemed to run fine. I tried one
> example that needed MIDI input without MIDI input and the app didn't crash,
> it just took me back to the main window.
>
> Greg
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"