Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
dev:bugs_todo [2009/11/20 14:12]
michael
dev:bugs_todo [2009/11/30 03:50]
michael
Line 2: Line 2:
 These should probably be filed on the tracker.  We'd like to fix this stuff before release, but these are the least significant problems, and our deadline is totally blown.  We don't want to miss the extended deadline to deal with these. These should probably be filed on the tracker.  We'd like to fix this stuff before release, but these are the least significant problems, and our deadline is totally blown.  We don't want to miss the extended deadline to deal with these.
  
 +  * Show annotations/LilyPond directives is broken in the notation editor, and I'm just leaving it broken.  It needs some fairly heavy sorting, and there are more important things to fix first.
 +
 +  * If you manage to get double clicking on an ornament to work (I've just discovered this has been buggy since Classic) the resulting ornament editor dialog is a mess.  Since it's difficult to get here and we might go five years before a user in the field ever noticed these problems, I've decided to let all of this go and not spend time fixing it up.
 +    - group box to the right "Triggered Segment Properties" needs a spacer or something to fix its nasty layout.
 +    - the event filters don't work (I fixed this in two other places already, but apparently not here)
 +    - has a Segment -> Edit With... that does nothing
 +    - has a vacant Help menu
 +    - Musical/Real/Raw times do not work
  
   * It would be nice to make sorting in the bank editor human readable.  Given a list of banks called (or differing only by) strings 1 30 7 3 50 10, they should be sorted 1 3 7 10 30 50 instead of 1 10 3 30 50 7.  I don't see any quick and reasonable way to accomplish this though.  QTreeWidget has a sortOrder() or similar, but you can choose between ascending and descending only, and it obviously sorts this kind of list the same way **ls** would, rather than the way **ls -v** would.  This looks like quite the little subproject, cooking up some subclass of QTreeWidget that can sort more intelligently or whatever solution suggests itself.  I tested Classic and found the same behavior, so this isn't a regression.  If this were on the bug tracker at SourceForge, I'd move it to the feature request tracker.   * It would be nice to make sorting in the bank editor human readable.  Given a list of banks called (or differing only by) strings 1 30 7 3 50 10, they should be sorted 1 3 7 10 30 50 instead of 1 10 3 30 50 7.  I don't see any quick and reasonable way to accomplish this though.  QTreeWidget has a sortOrder() or similar, but you can choose between ascending and descending only, and it obviously sorts this kind of list the same way **ls** would, rather than the way **ls -v** would.  This looks like quite the little subproject, cooking up some subclass of QTreeWidget that can sort more intelligently or whatever solution suggests itself.  I tested Classic and found the same behavior, so this isn't a regression.  If this were on the bug tracker at SourceForge, I'd move it to the feature request tracker.
Line 8: Line 16:
  
    * Matrix or notation, use the side wheels to zoom either axis independently.  The selection box outline doesn't take the scale factor into account, so it gets fat sides when zooming horizontally, fat top and bottom when zooming vertically.  Likewise the selection outlines around event bars.  [NOTE: a quick and easy way around this is to find the various places (I think there were three in total) where the pen is set to a width of 2, and change it to 0 to make it a "cosmetic pen."  A "cosmetic pen" always has a width of exactly one pixel, regardless of any transformations that may be applied, and applying this to the selection boxes (matrix and notation) and to the selection outlines (around matrix events) does solve the scaling problem very easily.  Unfortunately, a single pixel line just isn't bold enough to be effective (particularly for the matrix selection outlines) so I threw that patch in a drawer and didn't commit it.  Oh well.]    * Matrix or notation, use the side wheels to zoom either axis independently.  The selection box outline doesn't take the scale factor into account, so it gets fat sides when zooming horizontally, fat top and bottom when zooming vertically.  Likewise the selection outlines around event bars.  [NOTE: a quick and easy way around this is to find the various places (I think there were three in total) where the pen is set to a width of 2, and change it to 0 to make it a "cosmetic pen."  A "cosmetic pen" always has a width of exactly one pixel, regardless of any transformations that may be applied, and applying this to the selection boxes (matrix and notation) and to the selection outlines (around matrix events) does solve the scaling problem very easily.  Unfortunately, a single pixel line just isn't bold enough to be effective (particularly for the matrix selection outlines) so I threw that patch in a drawer and didn't commit it.  Oh well.]
- 
-   * Drag and drop in the audio file manager needs a complete rewrite 
  
    * Rotaries don't look particularly good, and could do with a total rewrite or very serious face lift    * Rotaries don't look particularly good, and could do with a total rewrite or very serious face lift
 
 
dev/bugs_todo.txt ยท Last modified: 2022/05/06 16:07 (external edit)
Recent changes RSS feed Creative Commons License Valid XHTML 1.0 Valid CSS Driven by DokuWiki