Select/Deselect All broken #58574

New Issue

Frode Lindeijer · 2018-12-03T02:17:37+01:00

Frode Lindeijer commented

2018-12-03 02:17:37 +01:00

System Information
Operating system: Linux Mint 64-bit
Graphics card: GeForce 840M

Blender Version
Broken: Blender 2.8 Beta 8c620c8e2b
Worked: Blender 2.79b

The hotkey for selecting and deselecting all (A by default) does not respond at times. Often it does work, but sometimes it fails to respond to up to about ten keystrokes in a row.

Exact steps for others to reproduce the error
Press 'A' repeatedly at different intervals in a 3D Viewport. If the error does not occur, try rotating the camera a bit.

**System Information** Operating system: Linux Mint 64-bit Graphics card: GeForce 840M **Blender Version** Broken: Blender 2.8 Beta 8c620c8e2b3 Worked: Blender 2.79b The hotkey for selecting and deselecting all (A by default) does not respond at times. Often it does work, but sometimes it fails to respond to up to about ten keystrokes in a row. **Exact steps for others to reproduce the error** Press 'A' repeatedly at different intervals in a 3D Viewport. If the error does not occur, try rotating the camera a bit.

Frode Lindeijer commented

2018-12-03 02:17:37 +01:00

Added subscriber: @FrodeLindeijer

blender-admin commented

2018-12-03 02:17:37 +01:00

#58878 was marked as duplicate of this issue

Campbell Barton commented

2018-12-03 02:23:10 +01:00

Added subscribers: @pablovazquez, @ideasman42

Pablo Vazquez was assigned by Campbell Barton

2018-12-03 02:23:10 +01:00

Campbell Barton commented

2018-12-03 02:23:10 +01:00

This is because the shortcut uses double-click event (like mouse double click).

@pablovazquez since we have a preference for 2.7x behavior, what do you think about removing this double-click functionality?

It's quite unusual for applications to use double-click for the keyboard, so not sure its a good default.

An alternative could be not to use a time limit on keyboard double click events, but think this is likely to backfire.

We could also close this as working-as-intended.

This is because the shortcut uses double-click event (like mouse double click). @pablovazquez since we have a preference for 2.7x behavior, what do you think about removing this double-click functionality? It's quite unusual for applications to use double-click for the keyboard, so not sure its a good default. An alternative could be not to use a time limit on keyboard double click events, but think this is likely to backfire. ---- We could also close this as working-as-intended.

Pablo Vazquez commented

2018-12-04 09:43:40 +01:00

The select tool has changed from being a toggle between two operators to now always do only one task. A always selects everything. De-select is now set to Alt+A (as shown in menus). This gives a consistent way to select/deselect regardless if there was something selected or not.
{F5808779, size=full}

What you experience is Double-tap A which is an alternative way for power users to quickly de-select. Probably some of those taps were counted as double-tap so that's why it felt weird. This is not advertised in the UI (but it should be in the manual) as it's an unusual way to access a key, the advertised way of doing it is Alt+A like shown in dropdowns and search.

You can bring the 2.7 behavior of A to select/Deselect toggle depending on whether there is a selection, go to User Preferences -> Input -> Select All Toggles.
{F5808810, size=full}

@ideasman42 I'm not attached to this in particular but I think if used in more places could catch on as a way to run the opposite of certain operators that use Alt, especially those far from Alt in the keyboard (like Alt+H could be H+H). It's unusual but so was right-click selection. If it brings trouble and confusion I'm fine with removing it. But this case in particular was due to expecting 2.7 behavior, not misclicking or so.

The select tool has changed from being a toggle between two operators to now always do only one task. `A` always selects everything. De-select is now set to `Alt+A` (as shown in menus). This gives a consistent way to select/deselect regardless if there was something selected or not. {[F5808779](https://archive.blender.org/developer/F5808779/Screenshot_from_2018-12-04_09-23-23.png), size=full} What you experience is Double-tap A which is an alternative way for power users to quickly de-select. Probably some of those taps were counted as double-tap so that's why it felt weird. This is not advertised in the UI (but it should be in the manual) as it's an unusual way to access a key, the advertised way of doing it is `Alt+A` like shown in dropdowns and search. You can bring the 2.7 behavior of `A` to select/Deselect toggle depending on whether there is a selection, go to User Preferences -> Input -> Select All Toggles. {[F5808810](https://archive.blender.org/developer/F5808810/Screenshot_from_2018-12-04_09-32-09.png), size=full} @ideasman42 I'm not attached to this in particular but I think if used in more places could catch on as a way to run the opposite of certain operators that use Alt, especially those far from Alt in the keyboard (like Alt+H could be H+H). It's unusual but so was right-click selection. If it brings trouble and confusion I'm fine with removing it. But this case in particular was due to expecting 2.7 behavior, not misclicking or so.

Brecht Van Lommel commented

2018-12-06 17:50:12 +01:00

Added subscribers: @Willzinator, @ZedDB

Brecht Van Lommel commented

2018-12-06 18:28:53 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2018-12-06 18:28:53 +01:00

I think the double-click A is problematic as well, in its current forum I would not keep it. It seems to have been some compromise, but now that there is a setting to change it, it makes less sense.

If we want to keep something like this, it seems better to make Select All test if all objects are selected, and in that case deselect all. That way you don't have to press the button within a certain amount of time.

I think the double-click A is problematic as well, in its current forum I would not keep it. It seems to have been some compromise, but now that there is a setting to change it, it makes less sense. If we want to keep something like this, it seems better to make Select All test if all objects are selected, and in that case deselect all. That way you don't have to press the button within a certain amount of time.

Luke Wills commented

2018-12-06 18:50:26 +01:00

Just saw this.

The toggle select in preferences helped a lot thank you very much. If I find anything else, I'll be sure to let you all know.

Thanks again and keep up the great work.

Just saw this. The toggle select in preferences helped a lot thank you very much. If I find anything else, I'll be sure to let you all know. Thanks again and keep up the great work.

Pablo Vazquez commented

2019-11-07 16:48:50 +01:00

Changed status from 'Open' to: 'Resolved'

Pablo Vazquez closed this issue

2019-11-07 16:48:50 +01:00

Pablo Vazquez removed their assignment 2019-11-07 16:48:50 +01:00

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

Select/Deselect All broken #58574