It doesn't seem to be logically correct to place it inside App/system because it is about blender internal staff and used more by advanced users/developers.
There is already a very nicely named File->Defaults menu, which points to the actual idea of the task - associating files/overriding defaults. What you guys think?

Ok, it seems I just needed to produce the full event key down -> key up, so I think issue is solved

Hi!
Very interesting and helpful addition!
Does this mean that it will be possible to execute somethng in-between modal operators as well (i.e. detect start and finish)?
I already have some ideas where it can improve my workflow a lot! Thanks!

In T84701#1093358, @Robert Guetzkow (rjg) wrote:

Are you using a mouse as input device?

Hi!
Same issue, consistently reproducible

This version also affected:
2.93.0 Alpha, branch: master, commit date: 2021-01-13 23:58, hash: rB0876829e7a77

And another one with blender_factory_startup.cmd:

Here is the crash with default Blender settings:

If I disable all my addons result is the same:

Hi!
Here is the files:

In T82722#1055694, @Philipp Oeser (lichtwerk) wrote:

For the three faces corner, every edge touching the vert is sharp, but as soon as one edge isnt (2 face example), it will average

In T82722#1055591, @Philipp Oeser (lichtwerk) wrote:

This is indeed unexpected, not sure this is really a bug though.

Code checks all participating edges of participating faces and if it finds one that is smooth it will do the averaging.
Think we can improve here though and check if the participating edge has only one face (in that case, it should not count as smooth)

Will keep on my desk as TODO.

Ok, after trying the disabled Select option I found out that there is at least 2 scenarios:

Maybe then it is better to disable this option by default since it doesn't make much sense.
Why there is a reason to select everything after unhide if this is already possible with pressing A (select all) and in 99 cases user working with not ALL objects but only part of scene?
It also seems like kind of industry standard in other software.

In D9399#233639, @Brecht Van Lommel (brecht) wrote:

The reason is that hide and select operators should not show an adjust last operation panel.

This is meant to be configured in the keymap, not every time you hide/unhide.

This one is a super welcome feature!
Right now selection is quiet inconvenient in edge mode, hope patch will find it way to the end!

After some research I found out that adding this callback to operator solves an issue:

Wow, does this mean we can finally get a checker overlay? (which is obviously a lot more needed rather than stretching, which is also have very confusing color theme imho)

Hi!
Label is normal on 2.83 39cf62607fe5.
But still weird that half of a panel on the left have a blank space.

Hi @Campbell Barton (campbellbarton). It seems that Ctrl-Spacebar doesn't work for view maximize anyway - it acts as space.
Broken: version: 2.82 (sub 3), branch: master, commit date: 2019-12-05 19:15, hash: rB61a02a7aa1ca

In T61474#675173, @Ludvik Koutny (rawalanche) wrote:

In T61474#675150, @Adrian Rutkowski (rrtk) wrote:

the problem is still there even with today's build

I think that saying its related to gizmo is super misleading.
It is way more noticeable when gizmos are present but it's still there without it

I mentioned that before on topic that was merged here, the problem is there only if other software ( even in the background) is not using the video card
Opening anything next to blender instance will give an instant speedup that includes Nvidia Experience Overlay which is enabled on GTX cards by default, so 99% of users will not even notice unless they disable everything.

Yes, exactly! Most people don't notice because they run lots of garbage in the background which prevents GPU from idling. Only in rare cases do people care about their system background processes remaining clean and not utilizing much of hardware resources. And only then this bug manifests. For some reason, in some cases, which include gizmos being visible, Blender keeps getting the GPU to idle, which causes constant lag spikes and stutter. I have to solve this by always launching OBS and keeping it running in the background, so that it keeps the GPU awake.

In T61474#674967, @Clément Foucault (fclem) wrote:

Did the situation improved with todays build?

In T64131#672000, @Sebastian Parborg (zeddb) wrote:

Can you try the latest blender beta and the latest nvidia drivers?