From CSWiki
Jump to: navigation, search

Here are some potentially "showstopper" or otherwise really undesirable bugs for using the miniAudicle for teaching/performance in PLOrk.

So far many of the really serious ones are related to weird/misleading behaviors in the mA editor, secondarily in preferences, including:

  • syntax highlighting weirdness
  • inconsistency in treating "invalid" tokens (miniAudicle doesn't display them, but they are there). this leads to all kinds of problems from being unable to save current buffers, weird "invalid token" messages when running the code in command line chuck, and I (ge) suspect that this may have something to do with the weird syntax highlighting.
  • indentation (it's important to have smart indentation, but it's too buggy to use currently)
  • in general, the mA seems quite crash prone, especially to new users
  • (preferences?) sometimes the mA starts with 0 DAC channels, a workaround is to open preferences, and select the channel numbers again.
  • on-the-fly visual feedback should be enabled by default.

Specific Bugs

Invalid Tokens

  • severity: showstopper (while this doesn't happen all the time, it can be highly frustrating/baffling when it does, affects power users and plork students alike. is there an easy fix to this?)
  • reported by: Dan (original) and Ge (entered on wiki with additions)
  • description: in the mA editor, invisible, "junk" characters linger:
    • they cause invalid tokens warnings when run in the command line chuck
    • sometimes, junk characters seem to be introduced from the editor itself (perhaps with accidental pressing of special key characters)
    • possibly causing incorrect syntax highlighting
    • occasional problems either closing or saving a buffer (sometimes, it gets such that you can do neither) - this sometimes happen when copying formatted text (e.g., from web) into the mA
  • files: check out code here
    • save this (rename to .ck if necessary), then open with miniAudicle. the first 56 lines are all green
    • (ge) copied and pasted into another mA buffer, then saved. things seem more sane here
  • verified by:
    • Perry (system config?)
    • Seth (system config?)
    • Ge-1 (see below)
    • Dan-1 (see below)

Smart Indentation Incorrect for things like "one-liners"

  • severity: high
  • reported by: Ge
  • description: when "smart indentation" is ON, it gets confused sometimes.
  • examples
    fun void foo()
        if( true ) <<< 1 >>>;
    if( maybe ) <<< "maybe" >>>;

The line starting with 'if( maybe )', is forced to the left/margin. Furthermore, it's impossible to space/tab that line regardless of whether the "tab smart indents current line" is ON or OFF. fixed in cvs

    if( true )
        // until()
        0 => int j;
    0 => int i;
  • verified by:
    • Ge-1
    • spencer-1

on-the-fly visual feedback should be on by default

  • severity: medium, feature request
  • reported by: Ge
  • description: please enable the on-the-fly visual feedback in preferences by default, it's a really useful que, and as far as I know has not caused problems. this will probably only affect machines installing mA for the first time.

comment colorizing

  • severity: medium/severe
  • reported by: Dan
  • description: when adding or editing comments contained within /* */ on multiple lines, colorizing doesn't happen until the file is closed/reopen.

tabbing not allowed

  • severity: medium
  • reported by: Dan
  • description: can't tab arbitrarily when "tab key smart-indents line or selected text" is set. say you want to line a bunch of chuck symbols, for readability, so you tab a bunch to the appropriate place. can't do it in this situation. i've just turned it off for now, and maybe i don't understand what that feature is supposed to do, but it's weird to press tab and have nothing happen.

window positions/sizes

  • severity: medium, feature request
  • reported by: Dan
  • description: would be wonderful if mA could remember the positions and sizes of the VM, Console, and editor windows on reopening

function menu

  • severity: low, feature request
  • reported by: Dan
  • description: also be wonderful if mA had an autogenerated menu to find functions defined in a particular file, use #pragma marks, etc... the way many IDEs do. just noting things that made me want to work in Textwrangler in the first place. maybe i shouldn't do this, but i've got chuck files well over 1000 lines....


  • severity: low, feature request
  • reported by: Dan
  • description: also be great if there was a command-B (or some such) "balance" command, to check balancing on curly braces, parens, etc...

testers/users and machine configurations

To aid this bug hunt process, please make an entry for yourself:


  • (Ge-1) machine/OS: MacBook Pro / OS 10.4.11 | mA:: | ChucK:


  • (Spencer-1) machine/OS: MacBook Pro / OS 10.5.1 | mA:: | ChucK:


  • (Dan-1) machine/OS: MacBook / OS 10.4.11 | mA:: | ChucK: