Age | Commit message (Collapse) | Author |
|
|
|
This functor/closure is responsible for stealing focus from any existing text entry (or whatever else may have focus)
when clicking on a CairoWidget or derived class.
The old implementation just gave focus back to the editor canvas. The new version walks up the widget packing
heirarchy to find a focusable parent (from the CairoWidget for which it is invoked). If no focusable parent
is found, it cancels keyboard focus in the toplevel window containing the CairoWidget
|
|
|
|
|
|
This had become incoherent over time, and posed a development hazard and burden going forward
|
|
|
|
|
|
lookup from binding definition
We need this because we need binding information/objects before all
Actions have been defined.
|
|
|
|
|
|
This removes the ability to change bindings via menus.
Still to come: saving modified bindings, and reworking the key editor
|
|
We don't need this functionality anymore as we build on 15 years experience plus the new tabbed structure
|
|
I would have loved to split this apart, but there are just so many interrelated changes,
it makes little sense and would be a huge effort that would break future git bisect
use because so many intermediate commits would not compile
|
|
Add mark_in and mark_out actions that explicitly use the playhead as the edit location.
|
|
of the ui-actions, so they are easier to see and maintain
|
|
|
|
|
|
|
|
|
|
Paul Davis was responsible for introducing almost all of this.
|
|
This reverts commit ebb43508f1ab75b7d7467e0e95cdd1c816cf3183.
|
|
|
|
This removes the direct dependence on ardour_ui.h from 39 files
|
|
Set-Loop-Start/End-From-Edit-Point
Set-Punch-Start/End-From-Edit-Point
|
|
|
|
Signed-off-by: Damien Zammit <damien@zamaudio.com>
|
|
'Cut time' implies that the cut timeline items might end up on the
clipboard to be pasted somewhere: this isn't the case at present, so rename
the functions, class, &c. to say 'remove' rather than 'cut'.
Rename insert_time_dialog.{cc|h} to insert_remove_time_dialog while we're
at it.
|
|
|
|
|
|
|
|
|
|
Copy the 'Cut time' code from Mixbus, making a few obvious fixes to work in
A3 (e.g. nframes_t => framepos_t / framecnt_t).
Seems to work to move & remove markers, tempo & meter markers, and regions on
selected tracks.
Still TODO:
- use existing A3 'Insert time' dialogue
- make it respect 'No selection = all tracks'
- rename the command to something like 'Remove time' or 'Delete time': 'Cut'
sounds to me as if the removed range should end up on the clipboard ready
to be pasted somewhere, which of course it doesn't.
|
|
Still requires a way to make this work correctly from the mixer window
|
|
|
|
|
|
change name to fit-selection. remove action to zoom (both axes) because this can trivially be accomplished by clicking (f)it and (z)oom sequentially, and it frees a keybinding. remaining bug: Fitting a selection of MIDI regions doesnt work right
|
|
anyway). also fix a bug so you can drag the playhead and split at the playhead location
|
|
|
|
set ranges or zoom to selections are redundant. save some menu entries and keybindings by consolidating them. also consolidate some code with new function get_selection_extents(). as a side-effect, this checkin fixes the assert failure in play_with_preroll
|
|
|
|
|
|
The user can now replay *all* earlier selection operations until the next
session undo/redo command, or the completion of a new operation.
Nothing relating to selection ops is stored, and selection operation history
is begun on first idle.
Selection operation history is fundamentally different from the history of
operations which act on a selection in terms of both their viewport and the
amount of information required to replay them.
WRT undo, the user of a selection op doesn't care about the viewport state
at the beginning of an op, but rather that at the end of the previous one.
|
|
|
|
ToDo: zoom to selection of midi notes, control points, tracks(?)
|
|
RCConfiguration
|
|
|
|
|
|
There might be a few special cases lingering around from attempts at magic tool
business, but this seems to work fine as far as I can tell.
|
|
We're going to need the ability to apply MIDI edit operations to a note/control
selection soon...
|
|
This cleans up a lot of false-positives in static analysis
and also helps compilers to optimize code paths in general.
(tagging the fatal stingstream operator as ‘noreturn’ is
far less trivial)
|