From CSWiki
Revision as of 03:30, 6 January 2008 by Gewang (talk | contribs)

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 Trueman (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
  • verified by:
    • Dan (system config?)
    • Perry (system config?)
    • Seth (system config?)
    • Ge-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, for example:
   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.

  • verified by:
    • Ge-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.

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: