In D14046#374768, @Hans Goudey (HooglyBoogly) wrote:

Thanks for the patch. I would rather avoid adding more hardcoded options to modifiers like this and push for a fully generic solution. With a bevel node in geometry nodes you could bevel any edges you wanted, with a selection, an angle, any flag, etc.
That's the way things are headed, and indeed, there is already task for such a node: T86841

Nice job with your first patch. I'll close this patch for the above reasons though.

Using new operator from D12307 works like a charm!
Thanks @Harley Acheson (harley) !

In T90731#1208042, @Harley Acheson (harley) wrote:

Interesting is that for both "Join" and new "Close", I'm pretty sure I can get them working as you want from python, except for the specific example you are showing here. So far I'm not finding a way of having Console destroy itself this way without a ton of hurt. I see solutions that will work with all other areas, but not situations where Console (or Text editor running a script) can close themselves. Not sure if that is a major issue though and I can show a nice error message in this situation.

@Harley Acheson (harley) yes, that's true - there is no way to set direction, so the only way I found for my add-on is to swap areas and after join them.
Yes, using area corner position and direction sounds like a great way to improve an operator!

In T90731#1207529, @Harley Acheson (harley) wrote:

Sorry, but not that familiar with using Python for this, so could you explain a bit better how this worked in earlier versions? Your “cursor” here is specifying a singular location at the top-left of one area. The code there has always started at the cursor location and expanded out to find two areas to join. But it could find 0-4 areas depending on where that point is. So I think you’d also have to pass a join direction for it to know what to do, otherwise how do you specify which area is subsumed by the other?

It actually seems that many of the operators breaks if properties are cleared.

In T88625#1167115, @Pratik Borhade (PratikPB2123) wrote:

@Oleg (DotBow) , Not sure I understand the problem, do you mean to say selecting a face in UV editor and then pressing Shift+H only highlights face of one object instead of both objects faces in viewport?

If that's the case then I can confirm the report.

(Again, Philipp commented here already and I did not notice that :p)

In T88625#1167084, @Siddhartha Jejurkar (sidd017) wrote:

Couldn't reproduce this on the latest 3.0 Alpha, but I was able to reproduce this on 2.80 release
The issue was possibly fixed in T75974.

It doesn't seem to be logically correct to place it inside App/system because it is about blender internal stuff 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. I think it is a lot easier and convenient for either new or old users to find it there.
What you guys think?

Ok, it seems I just needed to produce the full event key down -> key up, so I think the 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)