> On 18 May 2022, at 11:50, Laszlo Papp wrote:
>>
>>
>>
>> On Wed, May 18, 2022 at 9:50 AM Volker Hilsheimer
>> wrote:
>> > On 18 May 2022, at 10:09, Laszlo Papp wrote:
>> >> On Wed, May 18, 2022 at 9:03 AM Volker Hilsheimer
>> >> wrote:
>> >> Have you ever used vim? :P Deleting until
On Wed, May 18, 2022 at 10:50 AM Laszlo Papp wrote:
> 1. Single combination
> 2. Finishing character
> 3. No timer! This could be done automatically for keyPressEvent timing. No
> need to time again in a custom widget.
> 4. Allowing Esc to be assigned like in some apps.
>
5. Property to cancel
On Wed, May 18, 2022 at 9:50 AM Volker Hilsheimer
wrote:
> > On 18 May 2022, at 10:09, Laszlo Papp wrote:
> >> On Wed, May 18, 2022 at 9:03 AM Volker Hilsheimer <
> volker.hilshei...@qt.io> wrote:
> >> Have you ever used vim? :P Deleting until the end of the line, or
> deleting the next word,
On 2022 May 18, at 11:21, Eike Ziller
mailto:eike.zil...@qt.io>> wrote:
We have several multiple-chord shortcuts in Qt Creator, at least for code
pasting, test integration, version control system integration, and editor
splitting/navigation.
At some point the space for single chord shortcuts
> On 18 May 2022, at 10:09, Laszlo Papp wrote:
>
>
>
> On Wed, May 18, 2022 at 9:03 AM Volker Hilsheimer
> wrote:
>> Have you ever used vim? :P Deleting until the end of the line, or deleting
>> the next word, are all multi-chord key sequences.
>
> Sure, but in this context, we were
> On 18 May 2022, at 10:09, Laszlo Papp wrote:
>> On Wed, May 18, 2022 at 9:03 AM Volker Hilsheimer
>> wrote:
>> Have you ever used vim? :P Deleting until the end of the line, or deleting
>> the next word, are all multi-chord key sequences.
>
> Sure, but in this context, we were discussing
>
> This is also a questionable decision for a keyboard shortcut edit
> actually. Quite often, shortcut editors would terminate the shortcut after
> you entered it or with return if they do not want to allow that shortcut. I
> have actually never seen a shortcut edit which terminates by some
>
On Wed, May 18, 2022 at 9:03 AM Volker Hilsheimer
wrote:
> Have you ever used vim? :P Deleting until the end of the line, or deleting
> the next word, are all multi-chord key sequences.
>
Sure, but in this context, we were discussing shortcut editors that was
linked in KDE.
> > The current
> On 18 May 2022, at 09:45, Laszlo Papp wrote:
>
> As a datapoint
> https://api.kde.org/frameworks/kguiaddons/html/classKeySequenceRecorder.html
> (which
> supports single letter shortcuts, used by KShortcutsDialog and co.).
>
> Thanks for sharing that.
>
> I do not know where the idea of
>
> As a datapoint
> https://api.kde.org/frameworks/kguiaddons/html/classKeySequenceRecorder.html
> (which
> supports single letter shortcuts, used by KShortcutsDialog and co.).
>
Thanks for sharing that.
I do not know where the idea of "key sequence" comes from, but it does look
like what we
On 16/5/22 19:12, Laszlo Papp wrote:
On Mon, May 16, 2022 at 2:57 PM Volker Hilsheimer
wrote:
On 11 May 2022, at 16:02, Laszlo Papp wrote:
Hi,
1. I would like QKeySequenceEdit to block the processing of hotkeys
while recording, so that the new hotkey being recorded is not getting
>
> > 2. Is it possible to configure QKeySequenceEdit not to support multiple
> keypresses as a shortcut for an action? It seems to be the default
> behaviour and it feels a bit odd at first. At least, not how we would like
> to use this. I am referring to the "A, B, C" setup that is possible. If
> On 16 May 2022, at 19:44, Laszlo Papp wrote:
>
>
>
> I’ll have to look a bit more, but looking at the code I see that
> QKeySequenceEdit accepts both the ShortcutOverride and the Shortcut event, so
> it should take precedence over any application-defined shortcut. If/since
> that
I’ll have to look a bit more, but looking at the code I see that
>> QKeySequenceEdit accepts both the ShortcutOverride and the Shortcut event,
>> so it should take precedence over any application-defined shortcut.
>> If/since that doesn’t work,
>>
>> But since you write cmd+q (and considering your
On Mon, May 16, 2022 at 2:57 PM Volker Hilsheimer
wrote:
>
>
> > On 11 May 2022, at 16:02, Laszlo Papp wrote:
> >
> > Hi,
> >
> > 1. I would like QKeySequenceEdit to block the processing of hotkeys
> while recording, so that the new hotkey being recorded is not getting
> handled (e.g. cmd+q
> On 11 May 2022, at 16:02, Laszlo Papp wrote:
>
> Hi,
>
> 1. I would like QKeySequenceEdit to block the processing of hotkeys while
> recording, so that the new hotkey being recorded is not getting handled (e.g.
> cmd+q does not close the Qt app in this mode).
>
> Is this already
Hi,
1. I would like QKeySequenceEdit to block the processing of hotkeys while
recording, so that the new hotkey being recorded is not getting handled
(e.g. cmd+q does not close the Qt app in this mode).
Is this already possible to achieve? I think that modal dialogs work ok for
example. But in
17 matches
Mail list logo
