View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003162 | ardour | bugs | public | 2010-05-22 12:30 | 2020-04-19 20:14 |
| Reporter | paul | Assigned To | cth103 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 3.0-beta1 | ||||
| Summary | 0003162: trim-drag of MIDI regions is really slow | ||||
| Description | trim-drag of MIDI regions is really, really slow | ||||
| Tags | No tags attached. | ||||
|
|
MidiRegionView::redisplay_model is called on every mouse movement, since regions are actually trimmed in real-time as the mouse is dragged. I can't see any obvious optimisation to this method; the update_note() calls are quite expensive but necessary for a few of the notes to stop them overhanging the trimmed region view. Otherwise one could perhaps trim the region's rectangle during drag, leaving the notes behind, and then update on button release. |
|
|
i think the latter option will have to be the plan for this. |
|
|
Latter option implemented in SVN. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-05-22 12:30 | paul | New Issue | |
| 2010-05-22 12:30 | paul | cost | => 0.00 |
| 2010-05-22 13:43 | cth103 | Target Version | => 3.0-beta1 |
| 2010-05-22 13:44 | cth103 | Status | new => confirmed |
| 2010-06-28 01:46 | cth103 | Note Added: 0008338 | |
| 2010-06-28 02:05 | paul | Note Added: 0008342 | |
| 2010-06-28 18:44 | cth103 | Note Added: 0008349 | |
| 2010-06-28 18:44 | cth103 | Status | confirmed => resolved |
| 2010-06-28 18:44 | cth103 | Resolution | open => fixed |
| 2010-06-28 18:44 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:14 | system | Note Added: 0022077 | |
| 2020-04-19 20:14 | system | Status | resolved => closed |
