Posted request for platform spesific key conflicts here: https://devtalk.blender.org/t/platform-spesific-key-conflicts/7395

In T55194#681357, @Ramesh LD (RameshLD) wrote:

Mesh Tools:
Deform_ Slide edge-Vertex

I think that this task is complete for now. We should start a new task for a real tool in the toolbar for a 2.81 or later. Since such tools are typically interactive, some possibilities would be:

• the modal "point normals at" command (maybe with custom gizmo to help)
• the modal "rotate normals" command (currently pretty hidden under rotate transform with n typed afterwards)
• a new modal "set face strength" command, to let you select and set multiple faces' strengths in sequence; ideally combined with custom drawing to show which faces have which strength
• maybe a way to display the numeric values (vector) of selected normals (like a 'measureit' for normals)?

@Brecht Van Lommel (brecht) said it made more sense to simply remove the checks for "active lights" since we no longer have such a concept.

@Campbell Barton (campbellbarton) assigning to you to ensure you see that task, we really need input from event master here. Why do we break event handling when operator returns (OPERATOR_PASS_THROUGH | OPERATOR_RUNNING_MODAL), at the end of wm_handler_operator_call()? This seems the opposite of PASSTHROUGH idea to me.

D4900: Color Management: update configuration, remove legacy transforms

Changes to this patch:

I'm a Windows user, but after the initial "What the heck" reaction, I didn't mind it being an icon and having those Mac-like way of doing things, since an icon is small and distinguished.
Of course, the problem is users may not understand it to be a button, and it's a highly non-standard behavior on Windows.

Top to bottom makes sense if undo history was a panel. As a menu I doubt it, if you have a very long undo history then the most recent entries will be scrolled off screen or far away from the mouse. There would need to be some solution for that, but I can't think of an elegant one.

Looks good, just add static before committing.

Same behaviour "bug?" on three different computer at work.

Not exactly the same bug, but root cause is the same.

While those settings work well for video editing, several of them don’t work for normal 3D modeling & animation. Unfortunately, Preferences are not stored in the workspace so we can’t really set different preferences when starting a video editing project.

Sorry for being late. Here are a few suggestions for the sequencer startup presets:
(from: https://devtalk.blender.org/t/suggestions-for-vse-ui-cleanup-and-default-settings-in-2-8/2210 )