What do you mean by the tool mode?

Where is cycle option?

I think cycle option works different. It's already in Blender 2.8 default by using W key in 3d Viewport.

If Some tool have e.g. hundred of sub menus then cycle through is a lot of pain for user.

I this it's easy for user to just selects last tool (active one) which is shown in the tool bar to select with keyboard. like he can select with mouse

Cycling through item's is different from directly selection last item (active) like if you are currently selected move tool and directly want to select box select tool.

In T63392#688548, @Campbell Barton (campbellbarton) wrote:

Talked online, this is already supported, enable cycle option in the keymap.

Sorry but I don't think you understood the issue. It's not about cycling the mode. It's about making the mode persistent. So that if you switch to a different tool and switch back to select tool, you are able to switch back to last select tool mode. Please read the report carefully, especially the reproduction steps. Thank you.

What I meant is that the Select Tool, the button on the tool panel, can be in in multiple modes:
Box select
Circle Select
Lasso select
Single select

If you set the Select Tool mode to circle select for example, then switch to Move Tool, and then use HOTKEY to switch back to Select Tool, it won't switch back to Circle Select, but instead changes the mode back to Box Select. It is not possible to assign the select tool itself to a keymap, only a specific mode of the select tool.

At the same time, it is possible to CLICK on the Select Tool button, to go back to it without changing its mode. So here's an action that can be activated using mouse click, but not a keyboard shortcut.

I have no idea how else to explain it.

Currently using keymaps you can activate a spesific tool directly, or you can cycle the group of tools (which first activates the group, then cycles).

If we want some additional ways to activate tools they can be added - but it's a feature request.

In T63392#688789, @Campbell Barton (campbellbarton) wrote:

Currently using keymaps you can activate a spesific tool directly, or you can cycle the group of tools (which first activates the group, then cycles).

If we want some additional ways to activate tools they can be added - but it's a feature request.

Why was it confirmed and tagged as high priority by a person responsible for 2.8 UI then? Isn't impossibility to preserve a tool state selected by the user severe enough usability issue? 2.8 relies on the tool system, I doubt anyone will be happy with their tools forgetting their state as long as they use hotkeys.

@Ludvik Koutny (rawalanche) if you use cycle it preserves the select state, it just cycles after you press it again.

Maybe it's just the Industry Compatible keymap that needs a tweak to use cycle?

I remember cycle not working the way it does now. But it seems to be working well now as far as I can tell. It might have changed at some point (perhaps even before this report), or I'm misremembering.

This didn't change for a long time.

Note that we could have additional behavior

mode = [
  `SET`,                 # current default.
  `SET_GROUP_OR_CYCLE`,  # current cycle=True behavior.
  `SET_GROUP`,           # new behavior, matches clicking on the button  (never cycles).
]

Altough cycling seems more useful, the only reason you'd not want to cycle is if you want to have a key set a tool and be able to press it multiple times without worrying if it's active or not.

This seems one of many things that could be different, but not high priority.

Actually, It works exactly as the proposed bug, idea or feature expects.

Only cycle option is confusing for general users, means he/she have to know about for this only small feature.

Just to clear to new users, it works in this way:

I think, currently only limitation are:

• Your have to go to pre->keymapfor this feature, I think it should be automatic assigned cycle (e.g. if assign short-cut to parent icon (tool-bar) then cycle because user can assign individual shortcut to each icon by opening sub menu and assign short-cut there, like as shown:

• Also when cycle user can not see assign short-cut to that's icon (e.g. it's moved), Although for sub icon short-cut can be see easily (e.g. tool-tip and sub-menu)

In T63392#689299, @Campbell Barton (campbellbarton) wrote:

@Ludvik Koutny (rawalanche) if you use cycle it preserves the select state, it just cycles after you press it again.

Yes, but this is *extremely* inconvenient, as it messes up your select tool mode any time you press it once more, which happens very often. It's a lot easier to just press select tool key for a good measure, than to actually look for which tool you have active. ESPECIALLY when you have the toolbar hidden. Having cycle behavior by default is a huge mistake.

To be very clear. Cycling of the tool modes is in no way a replacement for remembering the tool mode when activated through a hotkey. Cycling is also very inefficient way of getting directly to a tool mode you want. Can you possibly imagine having to press a key 3 times to enter the 4th mode of the tool every single time you switch back to that tool? That'd be a horrifying workflow.

All that is really needed is to have additional keymap operator that activates a toolbar tool instead of directly activating a tool mode. It is already doable by a mouse click. There is no reason it should not be doable using a hotkey press too.

In T63392#689488, @Ludvik Koutny (rawalanche) wrote:

In T63392#689299, @Campbell Barton (campbellbarton) wrote:

@Ludvik Koutny (rawalanche) if you use cycle it preserves the select state, it just cycles after you press it again.

Yes, but this is *extremely* inconvenient, as it messes up your select tool mode any time you press it once more, which happens very often. It's a lot easier to just press select tool key for a good measure, than to actually look for which tool you have active. ESPECIALLY when you have the toolbar hidden. Having cycle behavior by default is a huge mistake.

To be very clear. Cycling of the tool modes is in no way a replacement for remembering the tool mode when activated through a hotkey. Cycling is also very inefficient way of getting directly to a tool mode you want. Can you possibly imagine having to press a key 3 times to enter the 4th mode of the tool every single time you switch back to that tool? That'd be a horrifying workflow.

Toatlly Agree!