| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:qt4_bug_tracker [2009/12/18 15:48]
michael |
dev:qt4_bug_tracker [2009/12/20 16:44]
yguillemot |
| [[bugs_todo|Bugs we can release with to make the deadline]] | [[bugs_todo|Bugs we can release with to make the deadline]] |
| ===Bugs in the Matrix=== | ===Bugs in the Matrix=== |
| * Selecting a quantisation in the matrix doesn't apply/change anything. | |
| |
| * Matrix cursor control needs sorting to follow the notation model once it's finalized (waiting so we can just copy it all at once instead of continuously feeding one to the other) | |
| |
| * Stacking order is not always correct for events with multiple segments open. You can often see this by making a selection and observing the "blue halo" appear around notes that are greyed out, because there are other notes in the active segment hidden behind them. (I think I may have just fixed this one, but leaving it here for the moment because I'm not sure --cc) | |
| |
| * There are issues with the default audio path (~/rosegarden) not always being created on demand (or maybe never created on demand) which can lead to brokenness in assorted ways, like drag and drop failing. This report is a reminder stub. | |
| |
| ===Bugs in the Note Editor=== | ===Bugs in the Note Editor=== |
| |
| * Missing slots up the bazoo. See [[Missing Slots]] | |
| |
| * Status bar resurrected, but it's terribly broken | * Status bar resurrected, but it's terribly broken |
| |
| * Newly selected segment not highlighted properly following Prior/Next Segment navigation control | * Newly selected segment not highlighted properly following Prior/Next Segment navigation control (And after about two or three next/previous cycles, nothing is ever painted blue again, although the status bar shows a varying number of events selected, consistent with the selection that's supposed to have changed. I wonder about this one anyway. Should we really select everything? It seems like the failure to select is less a bug in of itself than the failure to do a better job of showing which bit of what is active now. Suggests putting inactive notes in an off color, or even drawing a different background under the active area. Probably all out of scope for Thorn.) |
| |
| * Just after a segment is opened the cursor is not shown (is this a bug ?) | * Just after a segment is opened the cursor is not shown (is this a bug ?) |
| |
| * Rosegarden goes segmentation fault while adding slur. | * Rosegarden goes segmentation fault while adding slur. (Yves? I can't repeat this. More details.) - Gentoo amd64. This: [[http://users.v-lo.krakow.pl/~bbiegun/misc/rosegarden.log]] is log for that event. - Bug 2918002 related? : the trace of this last bug shows a crash in NotePixmapFactory::makeSlur(). I can't reproduce any of them (yg). |
| | |
| | * Shift+drag repositioning is very seriously buggy, and not usable |
| |
| ===Bugs in the Arranger=== | ===Bugs in the Arranger=== |
| |
| ===Bugs anywhere else=== | ===Bugs anywhere else=== |
| * Audio or synth plugin dialog, the Editor button never enables (but the one in the IPB works) | * There are issues with the default audio path (~/rosegarden) not always being created on demand (or maybe never created on demand) which can lead to brokenness in assorted ways, like drag and drop failing. This report is a reminder stub. |
| |
| * quantize dialog, layout goes screwy when changing to legato quantize | * quantize dialog, layout goes screwy when changing to legato quantize |
| |
| * NASTY! I haven't tried to repeat with random files, but the one I've got here has two time changes and a tempo change. Open tempo/time editor, select the time change I'm trying to delete, hit the X icon, and it wipes out EVERYTHING IN THE DIALOG! Not just the selected item. Must investigate and fix this before February! | |
| |
| |
| ====Bugs that were listed above, now fixed==== | ====Bugs that were listed above, now fixed==== |
| | -Audio or synth plugin dialog, the Editor button never enables (but the one in the IPB works) (Never fixed properly, but good enough for now. Hack the thing always enabled. Not ideal, but I didn't find any serious side effects. (Same thing with the "(no object)" warning. There are ghosts in this machine, but they seem fairly benign.) |
| | - NASTY! Tempo/Time editor delete function got horribly mangled in translation, and the new implementation was obviously hasty, without much real thought about what any of it was for. |
| | - Selecting a quantisation in the matrix doesn't apply/change anything. (Ironed out selection state whatnots so the Q is disabled unless there is a selection. I have no idea what the Quantize combo is supposed to do, but if I make a selection and then change its value, the selection goes away, implying something happened.) |
| | - Matrix cursor control needs sorting |
| | - Stacking order is not always correct for events with multiple segments open. (Doesn't seem completely credible, but it's a lot less glitchy than when originally reported.) |
| -**BUG** Quantize dialog layout needs some margins/padding, because group box contents are running over the group box labels. | -**BUG** Quantize dialog layout needs some margins/padding, because group box contents are running over the group box labels. |
| -**BUG** Quantize dialog goes VERY wide when the type combo changes to Legato. [Not really. It was staying the same width and getting much narrower contents without resizing properly. I settled for less than I wanted sorting that out, but it's good enough now. Just a little clunky instead of grossly clunky.] | -**BUG** Quantize dialog goes VERY wide when the type combo changes to Legato. [Not really. It was staying the same width and getting much narrower contents without resizing properly. I settled for less than I wanted sorting that out, but it's good enough now. Just a little clunky instead of grossly clunky.] |
