Re-opening the PR since as Harley noted Pablo did not review yet.
Although as noted, I'd rather this be handled as a design that others can comment on first.
@Rawalanche the intent isn't to close, it's to move the discussion to a design task.
The fact people are making suggestions here for how this might work differently - or different ways we might…
We have a few preferences like this, which users might not even know exist yet might want easier access to them. This is closer to having things “just work” rather than having to tweak…
@Harley firstly we can always re-open the PR (if you feel strongly about this).
That this was discussed in meeting is fine but this was not proposed in a way others could comment on who were…
The current function signature makes it useful as a callback, even after this change almost all callers are passing null for the second argument or using wrapper functions.
-
It's not communicated to the user which settings are preferences (and will impact other blender sessions).
-
This change doesn't scale.
If we have 2-3 preferences we can fit them in a…
Updated the PR, also moved the "Markers" key-map handler into wm_event_system.cc so it can be used by the check that excludes marker events.
The code is currently scattered about, noted to check functions that use UI_MARKER_MARGIN_Y, but I think this is a candidate for a refactor that adds functions to return the rcti for the…
As it happens this declarations looks to be redundant (the header includes both declarations), but I'll leave cleanups out of this PR.
From looking into this, some notes for the record:
Selection in animation/2D views uses fairly intricate logic to activate either: select-picking / tweak (select + translate) / box-select /…
Committed a3a3dda5632313d7f52231e2c2a54f4e36ed58a1.
When developing this I ended up having to make some changes the design proposed here.
The main difference is that a single extension can…