Re: [Qutecsound-users] Some issues with 0.5.0
Brought to you by:
mantaraya36
From: Felipe S. <fsa...@gm...> - 2010-05-10 17:11:24
|
Nice! Thanks for your work. On Mon, May 10, 2010 at 11:59, Andres Cabrera <man...@gm...> wrote: > Hi, > > I've now added this as well. The completion will not pop up if an > opcode has been already used in the line and if there is a '=' > character. There are actually some functions like int which could be > used in these cases, but the number of false entries that will pop up > I think justifies disabling the menu in these cases. > > Cheers, > Andrés > > On Sat, May 8, 2010 at 7:13 PM, Felipe Sateler <fsa...@gm...> wrote: >> On Sat, May 8, 2010 at 03:53, Andres Cabrera <man...@gm...> wrote: >>> Hola Felipe, >> >> Hola >> >>> >>> On Thu, May 6, 2010 at 8:22 PM, Felipe Sateler <fsa...@gm...> wrote: >>>> Hi all. I have a few issues to report, unfortunately :p. >>>> >>> >>> As long as it's not horrible crashing causing whole system meltdown >>> which damages the harddisk and the screen, I'm happy... =) >>> >>>> The autocompletion system is cool. However, it has some problems, as >>>> it triggers in unneeded scenarios. For example, if I'm writing a named >>>> instrument called printsomething, qutecsound will offer to >>>> autocomplete the print opcode. >>> >>> OK, now it doesn't pop up when "instr" or "opcode" text is before in >>> the current line. Any more scenarios that you can think of? >> >> I think so. If I understand csound correctly, opcodes can only occur >> within instrument or UDO context, so they can only happen in the orc >> (instr 0 allows opcodes). >> Therefore, opcode autocompletion should not happen in the score. >> Also, opcodes cannot happen in assignment context (asign = oscili >> 1,1,1 is wrong, right?). And finally, comments (which is not really >> wrong syntax, but maybe not really heplful). >> >> So, opcode autocompletion should be enabled only when all these >> conditions apply: >> 1. In instr/opcode context (only in the orc section) >> 2. No operators have been written in this line (+ - = etc). >> 3. Not in a comment >> 4. No keyword is before the cursor (I can't nest opcodes). >> >>>> <more issues> >>> Done. >>> >> <snip> >>> Fixed. >> >> Cool :). >> >> >>>> On another front, the output console prints red output for errors. >>>> Good. But if I have harmless errors,it puts the whole screen in red. >>>> For example, if my environment doesn't have RAWWAVE_PATH defined, then >>>> the stk opcodes will print: >>>> >>>> Error: define environment variable RAWWAVE_PATH >>>> (points to rawwaves directory) to use STK opcodes. >>>> >>>> >>>> And then on the whole output will be red, even though csound is >>>> running perfectly because my csd doesn't have stk opcodes in it. >>>> >>>> And really finally: I think the Shift+F1 shortcut should not redirect >>>> to the index page if something was not found. It should just be there >>>> and somehow notify the user (status bar?). >>>> >>> >>> I've filed theses two in the tracker, to look at them later: >>> https://sourceforge.net/tracker/?group_id=227265 >>> >>> Thanks for the feedback. >> >> Thanks for the application ;). >> >> -- >> >> Saludos, >> Felipe Sateler >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Qutecsound-users mailing list >> Qut...@li... >> https://lists.sourceforge.net/lists/listinfo/qutecsound-users >> > > > > -- > > > Andrés > > ------------------------------------------------------------------------------ > > _______________________________________________ > Qutecsound-users mailing list > Qut...@li... > https://lists.sourceforge.net/lists/listinfo/qutecsound-users > -- Saludos, Felipe Sateler |