- User Since
- Aug 15 2019, 11:40 PM (4 w, 6 d)
Is the end goal a true vim-style leader key system, or a version of the wm.toolbar operator that uses UI overlays instead of a popover?
Mon, Sep 16
Snap Cursor to Selected uses your pivot point settings. When you set the pivot to Median Point, as you have in your screenshots, it moves the cursor to the median point instead of the bounding box center.
I can reproduce the error by enabling Pie Menu Editor, in both default and modified configurations. Doesn't produce any console errors. I've pinged roaoao on BlenderArtists.
Thu, Sep 5
Sat, Aug 31
I'm still getting up to speed on the website but I can add this to my list of things to look into.
Using the OSkey is a no-go on Windows. It breaks convention and produces unwanted behavior on key release, Suppressing that behavior would get messy, interfering with expected OS behavior. The OSkey is in a great position, but it comes with a ton of baggage (on Windows).
I can reproduce. This issue produces a lot of console spam when you transform with functions (shearing by 1/tan(radians(60)), for example), since it throws a syntax error for each character you type. I'm not sure how hacky of a fix is appropriate here.
It looks like it's an issue of selected tracks vs selects strips, rather than selected vs active. Clicking on a strip selects both the strip and the track, while Select Prev/Next, Select All, and Box Select only select the strips. Further, with Deselect on Nothing enabled (as it is by default) box-selecting automatically deselects the tracks. All together, this makes predicting the selection state of strips and tracks harder than it needs to be. Some keymap tweaks, and a better visual indicator for track selection states, would make these behaviors a lot more predictable, but I haven't had a chance test it out with more complex animations.
Fri, Aug 30
If the goal is to minimize the keymap impact, we could swap the right-click menus from press to click, use right tweak for panning, and set the modifier keys to swap between Move/Rotate/Zoom within the modals. We'd have to adjust the stencil controls for painting and sculpting, but we should be able to nudge things around and use Ctrl+Shift and Ctrl+Alt+Shift for displaced functions. It feels pretty smooth when you're using a tablet, with or without Confirm on Release.
I've had a good experience using Spacebar as an MMB stand-in on laptops, re-mapping the standard actions (search, play animation, maximize area, etc) to double-click and using click-drag for rotating the viewport. I like enough that I use a similar keymap layering system on my desktop, as it lets me use Spacebar as a modifier key for LMB and RMB, too.
Sun, Aug 25
If you set your pivot point to Individual Origins and select all linked objects with Ctrl + L before transforming, it has the same effect as applying an object-space offset. We'll need to put more work into documentation/NUO if 2.81 ships without an auto-offset toggle, but I wouldn't be too worried about it in the short-term.
Sat, Aug 24
I'm in favor of setting top-level transformation modes (move selection, move origins, move cursor, etc) with an operator enum property. It would let us use operator enum pies for quick adjustments and it'd work well with the active tool system (tool settings header), but It wouldn't solve the problem of general header/header popover integration. It would put the features in predictable places, though, which should satisfy most users.
Fri, Aug 23
The feature's still there; you just have to hold Alt while you're making adjustments.
Tue, Aug 20
This is something @Germano Cavalcante (mano-wii) should look at; I'm a bit out of my depth here with the select engine.
Launch Blender with the blender_debug_gpu.cmd script (it's in the same folder as the executable) and post the log as an attachment. This might be related to a shader compile error that occurs on systems using Intel integrated graphics.
Aug 18 2019
I think we could take advantage of the tool system here. It's an easy way to dodge keymap conflicts and introduce niche operators without changing the learning curve. Add in a "Send To..." dialog that behaves similarly to the operator search dialog and you'd have a solid foundation for building new features.
I can reproduce. Keymap entries set to click won't activate on click-drag in general. A quick/temporary fix would be to use press events for the relevant entries when the drag pies are disabled.
Aug 16 2019
That particular shade of purple is a non-starter for people with Protanopia and Deutanopia; blends in with the Z axis. A more distinct handle shape and/or pull direction would make the color less relevant, though.
Aug 15 2019
I'd be in favor of letting users treat numlock/capslock states as (optional) modifier keys. It'd be more in-line with user expectations and it would produce fewer unexpected behaviors than what's proposed here.