[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Denemo-devel] Shortcuts - Final Touches
From: |
Nils Gey |
Subject: |
[Denemo-devel] Shortcuts - Final Touches |
Date: |
Sun, 27 Jun 2010 23:59:27 +0200 |
Some questions and requests:
0) Is there already a regression in Caps + Numbers? In default mode a number
inserts a non-printing note, shift+number changes the duration of a real note,
but caps+number does not change but still inserts a non-printing. I can confirm
this even with different keybindings, I tried it with number=insertNote,
shift+number=insertRest but caps+number is still insertnote.
1) What is the starting path for LoadKeybindings? It seems not to be ~/.denemo/
or ~/.denemo/actions because my .shortcut files are there but LoadKeybindings
returns #f. An absolute path from / loads correctly. I think correct behaviour
would be to start from .denemo, then .denemo/downloads (or whatever the dir for
download scripts is), then /usr/.../denemo .
Sidenote: Although other Keybinding and Commandset functions are much less
attractive since LoadKeybindings is in the town they suffer from the same
problem
2) Is it possible to include/merge .shortcut files from within other shortcuts?
I'm thinking about splitting my commands over several shortcut files (well,
this is my current state) and include them from Composer.shortcuts as starting
point.
3) I think the default .shortcuts file should not be touched at all by the user
but instead any binding the user makes from within Denemo should be saved in a
seperate user.shortcuts (no matter if default, composer, arranger...) file
which can be easily spotted and backuped by the user and only contains the
actual changings, which makes the file small, portable and "clean.
This would reduce the complexity of the Keybinding menu, too, if there is only
Load/Save.
Changes in built-in commandsets and shortcuts are only done by Denemo-devs
anyway, and they/we know how even without creating a new Default.shortcuts from
within Denemo.
4) There is the need to bind Scheme (one-liners) directly to a key sometimes
(or often, matters how you script). Two suggestions, I like a) better.
a) Implementing the user.shortcuts files from 3) would make it safe to directly
use <scheme>command</scheme> in the commandset file and thus can be used in a
.shortcuts file. Since these are real commands they can be used like any other
with (d-AddKeybinding) or (d-GetId), the only difference is that there is no
extra file in the menu structure.
b) Creating new virtual commands directly from scheme? They get not saved but
use the (d-XY) syntax, so they can be bound to keys and react to
(d-AddKeybinding) or (d-GetId). This would enable script authors to create a
loop that generates commands.
5) Hidden commands with a keybinding get installed in the menu after first
invocation, with a WarningPopup. How about removing the PopUp and just print
out the message on the console? Popups get in the way generally and this is not
exactly a super-important warning like an error or "Save Changes?".
Or maybe the installation is not even intentional and hidden commands with a
keybinding could be allowed?
Nils
- [Denemo-devel] Shortcuts - Final Touches,
Nils Gey <=