I can't use the Keyboard Shortcuts "]" (select: "After Current Frames") in Dope Sheet Editor or Graph Editor #48847

New Issue

Jefferson Rausseo · 2016-07-14T01:24:48+02:00

Jefferson Rausseo commented

2016-07-14 01:24:48 +02:00

System Information
GNU/Linux Manjaro 64bits
Nvidia 8600 GT

Blender Version
Broken: 2.77 91bda21
Worked: 2.77a Official Build

Short description of error
If I try to use the Keyboard Shortcuts "]" (select: "After Current Frames") in Dope Sheet Editor or Graph Editor it does not work, but the Keyboard Shortcuts "[" (select: "Before Current Frames") is fine.

Exact steps for others to reproduce the error

Open the .blend file.
Press "[", is fine.
Press "]", without selection.

key_wrong.blend

**System Information** GNU/Linux Manjaro 64bits Nvidia 8600 GT **Blender Version** Broken: 2.77 91bda21 Worked: 2.77a Official Build **Short description of error** If I try to use the Keyboard Shortcuts "]" (select: "After Current Frames") in Dope Sheet Editor or Graph Editor it does not work, but the Keyboard Shortcuts "[" (select: "Before Current Frames") is fine. ![blender_git.png](https://archive.blender.org/developer/F322541/blender_git.png) ![blender_2.77a.png](https://archive.blender.org/developer/F322543/blender_2.77a.png) **Exact steps for others to reproduce the error** 1. Open the .blend file. 2. Press "[", is fine. 3. Press "]", without selection. [key_wrong.blend](https://archive.blender.org/developer/F322545/key_wrong.blend)

Jefferson Rausseo commented

2016-07-14 01:24:48 +02:00

Changed status to: 'Open'

Jefferson Rausseo commented

2016-07-14 01:24:48 +02:00

Added subscriber: @jefrau

Bastien Montagne commented

2016-07-15 16:01:00 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2016-07-15 16:01:00 +02:00

I don’t understand what the two screenshots are for here?

Anyway, please give us your keyboard layout, that kind of shortcut only works fine with US qwerty keyboard iirc. At least here on my french keyboard, ] works OK but [, which is same key as 5, is eaten/replaced by 5 (that’s a 'hack' to make layer switching work with all keyboard layouts). As a rule of thumb, any shortcut which needs a modifier key (shift or alt-gr) on a given layout is likely to not work, Blender is designed by default for English QWERTY layout.

I don’t understand what the two screenshots are for here? Anyway, please give us your keyboard layout, that kind of shortcut only works fine with US qwerty keyboard iirc. At least here on my french keyboard, `]` works OK but `[`, which is same key as `5`, is eaten/replaced by `5` (that’s a 'hack' to make layer switching work with all keyboard layouts). As a rule of thumb, any shortcut which needs a modifier key (shift or alt-gr) on a given layout is likely to not work, Blender is designed by default for English QWERTY layout.

Jefferson Rausseo commented

2016-07-15 17:24:40 +02:00

Keyboard layout: Generic 105-Key INTL.

I have not modified the keyboard layout in Blender. With the version 2.77a Build Official works fine, but my compilation 91bda21 not works fine.

I removed the folder "./config/blender/2.77" and still does not work fine.

Keyboard layout: Generic 105-Key INTL. I have not modified the keyboard layout in Blender. With the version 2.77a Build Official works fine, but my compilation 91bda21 not works fine. I removed the folder "./config/blender/2.77" and still does not work fine.

Bastien Montagne commented

2016-07-15 17:49:25 +02:00

Not aware of a Generic 105-Key INTL layout… please make a screenshot of your keybaord's layout.

Anyway, this shall not have anything to do with blender configuration… Can you try to enable event debugging (--debug-events commandline option) and attach here as text file what's printed in console when you hit [ and ] ?

Not aware of a `Generic 105-Key INTL` layout… please make a screenshot of your keybaord's layout. Anyway, this shall not have anything to do with blender configuration… Can you try to enable event debugging (`--debug-events` commandline option) and attach here as text file what's printed in console when you hit `[` and `]` ?

Jefferson Rausseo commented

2016-07-15 18:13:58 +02:00

Run with --debug-evets:

In Blender 2.77a Official Build:
I press "Alt Gr + [" -> wm_handlers_do_intern: handled! 'ACTION_OT_select_leftright'
I press "Alt Gr + ]" -> wm_handlers_do_intern: handled! 'ACTION_OT_select_leftright'

In Blender 2.77 compile 91bda21:
I press "Alt Gr + [" -> wm_handlers_do_intern: handled! 'ACTION_OT_select_leftright'
I press "Alt Gr + ]" -> Nothing happens.

Run with --debug-evets: In Blender 2.77a Official Build: I press "Alt Gr + [" -> wm_handlers_do_intern: handled! 'ACTION_OT_select_leftright' I press "Alt Gr + ]" -> wm_handlers_do_intern: handled! 'ACTION_OT_select_leftright' In Blender 2.77 compile 91bda21: I press "Alt Gr + [" -> wm_handlers_do_intern: handled! 'ACTION_OT_select_leftright' I press "Alt Gr + ]" -> Nothing happens. ![teclado.jpg](https://archive.blender.org/developer/F323220/teclado.jpg)

Bastien Montagne commented

2016-07-23 10:57:36 +02:00

You should get more than that with --debug-events option, all key events would be printed out in console - would allow us to see what events is actually generated by your 'altgr-]' (my bet would be, it generates a '+' event instead). Please attach here as text file what's printed out by Blender in console when you hit those two keys.

But again, altgr-keys shortcuts are rather fragile and not always working with Blender, that’s known limitation more than a bug.

You should get more than that with `--debug-events` option, all key events would be printed out in console - would allow us to see what events is actually generated by your 'altgr-]' (my bet would be, it generates a '+' event instead). Please attach here as text file what's printed out by Blender in console when you hit those two keys. But again, altgr-keys shortcuts are rather fragile and not always working with Blender, that’s known limitation more than a bug.

Bastien Montagne commented

2016-07-29 15:42:28 +02:00

OK… so turned out release builds were not printing out same things as debug builds (thanks Sergey for finding that out). As been fixed today in master, so please redo the check with build of tomorrow and attach here console output. ;)

Jefferson Rausseo commented

2016-07-30 14:53:22 +02:00

With my compilation (e20d306):

Dope sheet: Not work
Dope sheet (my compile e20d306)
Text editor: Work
Text editor (my compile e20d306)

With Buildbot (3d7cf80):

Dope sheet: Not work
Dope sheet (buildbot 3d7cf80)
Text editor: Work
Text editor (buildbot 3d7cf80)

With 2.77a Official Release:

Dope sheet: Work
Dope sheet (Official Release 2.77a)

With my compilation (e20d306): - Dope sheet: Not work [Dope sheet (my compile e20d306)](https://archive.blender.org/developer/F329999/Dope_sheet__my_compile_e20d306_) - Text editor: Work [Text editor (my compile e20d306)](https://archive.blender.org/developer/F330000/Text_editor__my_compile_e20d306_) With Buildbot (3d7cf80): - Dope sheet: Not work [Dope sheet (buildbot 3d7cf80)](https://archive.blender.org/developer/F330001/Dope_sheet__buildbot_3d7cf80_) - Text editor: Work [Text editor (buildbot 3d7cf80)](https://archive.blender.org/developer/F330002/Text_editor__buildbot_3d7cf80_) With 2.77a Official Release: - Dope sheet: Work [Dope sheet (Official Release 2.77a)](https://archive.blender.org/developer/F330003/Dope_sheet__Official_Release_2.77a_)

Bastien Montagne commented

2016-09-02 09:59:33 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2016-09-02 09:59:33 +02:00

Bastien Montagne self-assigned this 2016-09-02 09:59:33 +02:00

Bastien Montagne commented

2016-09-02 09:59:33 +02:00

Text editor is using utf8 value of the event, while shortcuts handling uses its type. As you can see in your logs, type of altgr-] is PLUS, when altgr-[ generates expected LEFT_BRACKET event. This is entirely handled through X11 system, we try to be smart and fallback to ascii value to generate our own Blender event type in case 'keytype' fails, but all in all, it boils down to: altgr-key (or shift-key) combinations are not designed for shortcuts, they may work in some cases, but there is no way for us to guarantee it.

In other words, either you use US keyboard layout with Blender, or accept to not be able to use pre-defined shortcuts using keys not directly accessible on your layout (i.e. without any shift or altgr trick), or define your own shortucts…

Text editor is using `utf8` value of the event, while shortcuts handling uses its `type`. As you can see in your logs, type of `altgr-]` is `PLUS`, when `altgr-[` generates expected `LEFT_BRACKET` event. This is entirely handled through X11 system, we try to be smart and fallback to ascii value to generate our own Blender event type in case 'keytype' fails, but all in all, it boils down to: altgr-key (or shift-key) combinations are not designed for shortcuts, they may work in some cases, but there is no way for us to guarantee it. In other words, either you use US keyboard layout with Blender, or accept to not be able to use pre-defined shortcuts using keys not directly accessible on your layout (i.e. without any shift or altgr trick), or define your own shortucts…

Bastien Montagne commented

2016-09-02 16:27:08 +02:00

On second thoughts, this shall be fixable, and is kind of same issue as #48911… have patch for it, so will merge this report together :)

Bastien Montagne commented

2016-09-02 16:27:46 +02:00

Closed as duplicate of #48911

Bastien Montagne closed this issue

2016-09-02 16:27:46 +02:00

blender-admin commented

2016-09-03 17:50:56 +02:00

This issue was referenced by 16cb939163

This issue was referenced by 16cb9391634dcc50ee674852b80c70ccb5f05c43

Bastien Montagne commented

2016-09-03 17:53:36 +02:00

Changed status from 'Duplicate' to: 'Resolved'

Danni Coy commented

2016-09-15 10:51:31 +02:00

Added subscriber: @DanielCoy

Danni Coy commented

2016-09-15 10:51:31 +02:00

Commit 16cb939163
Changes the behaviour of blender under X11 for non qwerty layouts in a really significant way.

Previously blender used the hardware keysim so that keys stayed in the same place no matter which keyboard layout is being used after this commit blender looks up the current layout keycode.

In an application like blender which is designed to be used with one hand on the keyboard and the other on a mouse/tablet the physical position of the key is way more important than what is printed on it and the current layout is designed to be ergonomic on a qwerty keyboard, the more the layout deviates from qwerty the less ergonomic it gets.

In my case I would be forced to choose between learning a much less ergomic layout from scratch, constantly switching keyboard layouts every time I want to enter text or rebinding practically every key in the application.

Commit 16cb9391634dcc50ee674852b80c70ccb5f05c43 Changes the behaviour of blender under X11 for non qwerty layouts in a really significant way. Previously blender used the hardware keysim so that keys stayed in the same place no matter which keyboard layout is being used after this commit blender looks up the current layout keycode. In an application like blender which is designed to be used with one hand on the keyboard and the other on a mouse/tablet the physical position of the key is *way* more important than what is printed on it and the current layout is designed to be ergonomic on a qwerty keyboard, the more the layout deviates from qwerty the less ergonomic it gets. In my case I would be forced to choose between learning a much less ergomic layout from scratch, constantly switching keyboard layouts every time I want to enter text or rebinding practically every key in the application.

Danni Coy commented

2016-09-15 12:04:28 +02:00

ok it seems that commit 56d2f4c20a
similtaneously fixes the problem then breaks it again in a different way.

could somebody try to explain to me what this commit is trying to do...

ok it seems that commit 56d2f4c20a8efcc839afbe31a3de2da15c34b54f similtaneously fixes the problem then breaks it again in a different way. could somebody try to explain to me what this commit is trying to do...

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

I can't use the Keyboard Shortcuts "]" (select: "After Current Frames") in Dope Sheet Editor or Graph Editor #48847