Finally I had to create a new @command node in myLeoSettings.leo. Its
headline is '@command find-quick-selected2 @key=Shift-Ctrl-F', and its body
is just 'c.executeMinibufferCommand("find-quick-selected")'.
All that hacking just to restore one simple shortcut :-(.
It did get me thinking though. I have been using Leo since the days when Tk
was the basic of GUI (don't remember exactly but for sure more than a
decade now). I consider myself as an experienced Leo user and I do enjoy
and use a lot of power it gives to its users. However, if it take several
hours for one experienced user to adjust one shortcut, how long would it
take for a newbie? It is not just question of a possible bug in Leo that
caused so much trouble. Very soon I imagine this bug will be fixed and
everything will be fine. It is question of design of Leo settings code.
I would gladly admit that the way Leo deals with the settings is perfectly
flexible and it is hard to imagine any kind of setting that can not be
easily represented in Leo. But is this flexibility really worth its price?
How much of that flexibility an ordinary user needs? I haven't touched
myLeosettings.leo for years except for those few situations when something
was changed in default settings that I was relying on. AFAIR every time it
took me considerable time to reread the documentation and to relearn the
proper way of making those changes. Today I thought that maybe my spelling
of shortcut specification is not correct. Is it shift-ctrl-f or
Shift-Ctrl-f or Shift-Ctrl-F or shift-control, or maybe it requires +
instead of -? And everytime I try another combination I must close and
reopen Leo to check whether Leo accepted my change or not. It is just too
much required from user. User should not be forced to remember such trivia.
Perhaps, it is designed to accept any of the combinations mentioned
before, but in case when it doesn't accept I can't be sure why. I thought
maybe it is important where is @shortcuts node located. Does it have to
have some label after @shortcuts? Does it need to be child of @keys node?
Or maybe it is affected by something else? How much easier it would be for
user to be offered one text-box to press any key combination and it
automatically binds to selected command?
That is another kind of flexibility. It doesn't offer too much flexibility
for the programmer but it certainly offers a lot flexibility to users.
I have to stop writing now. I am thankful for Leo as it is. I am not
complaining because it caused me some trouble. I am complaining in the name
of all those users who tried to use Leo and gave up because it wasn't too
friendly to them. I have some ideas, but right now I must go.
Vitalije
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
