• Rename 'Directions' menu to 'Viewpoint' (camera is not a direction)
• Moved 'Local View' & 'View Global/Local' back into main menu (not directions or viewpoints).
• Moved 'Screen Areas' back into main menu (to match all other view menus, rather adjust all view menu's at once, not make 3D view an exception).

Move 'Side of Active' out of 'Linked' menu, since it's not a linked action.

Generally fine, though I'd try avoid forcing looping over EnumPropertyItem - in many cases the flag can be used directly.

Resolved rB91bfdacde262c4df18ade2e5266e5c969bb5f3af

• Minor edits

• Resolve conflicts with recent changes to workspaces.
• Add rip as tools, also support recursive property setting

Applied changes for border and circle select to be used as tools to master,
updated this patch to use those changes.

Agree hiding is best during animation, although the manipulator will still need updating when animation is finished.

(Summary of IRC discussion)

Comments

In T53047#465442, @Julian Eisel (Severin) wrote:

I generally like where this is going. It pretty much covers what I had in mind, although you go a bit further:
I actually didn't expect we'd work on having operator settings available before execution during the 2.8 project. In my mind, we'd limit things to supporting manipulators as active tool. This would be a big improvement on its own and should be the first step IMHO.
Is the pre-execution operator/tool settings really something that should to be part of the early 2.8 releases? Not against it really, just wondering if this was considered. I'm a bit afraid it might have too many loose ends.

Comments

Position operator properties next to operator

Comments

Thanks for the update, again, generally fine - though pointed out some minor things.

This is one liner, submitted PR: https://github.com/IfcOpenShell/IfcOpenShell/pull/271

@Stanislav Ovcharov (Stan1), the knife tool can handle any geometry.

Only managed to redo this in blender2.8, looks like pointer checks resolve, assigning to Sergey.

@Duarte Farrajota Ramos (duarteframos): this is more a design question for how key-maps interact.

Generally LGTM, only minor issues noted inline.