| Age | Commit message (Collapse) | Author |
|---|
|
Previously, dragging a MIDI note and scrolling with scroll wheel
(to change velocity) made the note jump back to location before drag.
|
|
We no longer assume that Snap always uses the visible ruler lines.
If you want to snap to the grid, and ignore the users zoom scale, use SnapPref::SnapToGrid_Unscaled
This fixes 2 (known) oversights: "snap region(s) to grid" and "regions whose start are left of the canvas edge".
|
|
|
|
(by not invoking the global color change signal)
|
|
|
|
|
|
Separate Snap from Grid. Lots of naming changes.
Multiple simultaneous snap options allowed. Grid is one of the possible Snap options.
Grid uses the same data as the rulers. Replace complicated tempo_lines with simple grid_lines.
The Grid is zoom-scale-sensitive along with the rulers. If you are zoomed out, grid becomes coarser.
|
|
snapped_cursor is updated. This probably fixes other bugs as well.
|
|
Snapped Cursor is a line that follows the edit point, and indicates where the operation will occur.
This replaces and extends the line that appears with the Cut tool.
New associated preferences: snap_threshold and show_snap_cursor.
|
|
|
|
|
|
|
|
Generated by tools/f2s. Some hand-editing will be required in a few places to fix up comments related to timecode
and video in order to keep the legible
|
|
|
|
Fixes broken undo stack if no changes occurred.
Edit note dialog is currently the only user.
|
|
|
|
|
|
- freeze the correct playlists on fiorst move.
- only update the start offset of linked regions once the drag
has finished.
|
|
- the spray is limited to the first entered note.
- all new notes are selected (requires a selection change to
MRV::create_note_at()
|
|
- should fix 7105
|
|
|
|
- Hit::position still may not be set correctly,
but this patch eliminates the error for now.
|
|
|
|
|
|
- wysiwyg (during drag) when dragging more than one note across
a tempo change.
- introduces a muscal equivalent of snap_delta (only used for
note drags atm)
- split earliest note in selection into a separate function
- MRV::copy_selection() returns the equivalent _primary note
to avoid offset hell.
- RV::snap_frame_to_frame returns a MusicFrame
- prevent note drag moving before region start.
|
|
boost::shared_ptr<> (rather than returning an int)
|
|
|
|
|
|
- don't add a new SysEx canvas item every time we zoom or drag.
- speed up redisplay generally using PatchChange-like method
for finding items (find_canvas_sys_ex() in boost::unordered_map).
|
|
snap now fills in a struct (MusicFrame) which contins a snapped frame
along with a music divisor.
this gives useful information wrt magnetic snap which may or may not
have rounded to an exact musical position.
region position may now be set musically (using quarter notes for now).
this patch fixes several problems in the current code:
- dragging a list of music-locked regions now maintains correct
musical offsets within the list.
- splitting regions using magnetic snap works correctly (#7192)
- cut drag should now work correctly with magnetic snap.
- musical length of split midi regions is no longer frame based.
|
|
- as MRV removes invalid notes from the GR, we
can simply update all events after checking vertical visibility.
|
|
|
|
|
|
Probably some corner cases to be fixed, but pretty functional and largely modelled
on existing code (paste, drag, step add note etc.)
|
|
|
|
use boost::unordered_map as a note store for ghost & midi region
views.
as per otiginal method, only notes within regoin bounds are stored.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- also fixes patch changes appearing outside region bounds
when copied/trimmed.
|
|
- redisplay_model() does this for us.
|
|
- MGR uses a _note_group to hold events.
- MRV & MGR delete canvas notes directly from their note group.
- sysex is untested (it uses MRV note group).
|
|
|
|
- this requires that MidiGhostRegion::update_contents_height()
also controls visibility.
|
|
- MGR visibility is handled by update_note/hit()
MRV unconditionally updates MGR events
- remove MidiGhostRegion::update_range()
- rename set_contents_height -> update_contents_height
|
|
|
|
- mostly due to searching a multiset rather than a list of
canvas events.
|
