mudlet-makers team mailing list archive

[Eldar Erathis <eldarerathis@xxxxxxxxx>]

Well, I decided to test your situation in Mudlet. I added a Ctrl+S
keybinding in the script editor and connected it to saveOpenChanges().
This keybinding works as it should, and it saves a
trigger/alias/script/etc when you use it from the editor. Then I went
and tried to capture Ctrl+S as a macro and Mudlet wouldn't let me; it
called saveOpenChanges() instead. So by the looks of it, Mudlet would
need to disable all script editor shortcuts somehow when it goes into
"capture" mode, otherwise Qt won't let you capture something that's
defined as a shortcut.

On the bright side, that would be the only tweak to capture mode. I
assigned a macro to Ctrl+S, then went in and re-activated the keyboard
shortcut. Now when I'm in the editor I can save things with Ctrl+S, but
pressing it when the main window has focus calls the macro.

I'd personally suggest implementing a new function call that
creates/activates the keyboard shortcuts, then calling it in the
dlgTriggerEditor constructor. Then another function for clearing them
all can be put in, too. It would look cleanest that way IMHO.

-- 
Creating a macro with a modifier is non-standard and unintuitive
https://bugs.launchpad.net/bugs/380720
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.

Status in Mudlet the MUD client: New

Bug description:
It's a standard practice that when a user needs to set a macro, they enable the capture mode and press the modifier + macro to set it - not capture mode, modifier, capture mode again, and key.

This is really unintuitive and all it does is frustrate users because something standard doesn't work.