I think this plan is fine overall. Just two points I would like to stress (which may be obvious):

• Don't hesitate to do refactoring and renaming where needed, also of adjacent code, to make design changes more clear. There is obscure logic spread out through the code to deal with mesh vs. editmesh vs. cages and evaluated vs. original, unifying that in functions with clear names will help write correct code in the future.
• Feel free to skip bullet points if they don't have a significant impact in profiling. We can try to optimize in every little corner, but in the end it's about what has the biggest impact.

Any news on this needed and handy feature?

Closing, since this is working as expected.

Ok, marking it as know issue, since the priority is low and there are no plans to fix it soon.

From a UX standpoint I think this makes sense.

In T74186#879788, @Campbell Barton (campbellbarton) wrote:

@Paul Kotelevets (1D_Inc), noted, although I think we should first look into making the default shader faster - if this is even a bottleneck.

sure, but still, no advantages at all by this new behavior.

Updated to have consistent naming and comment styling.

Prior to rB3b8a14a3c072 it was not possible to change the rotation in the Adjust Last Operation HUD at all.
Now if you touch the rotation, it changes back to WORLD, because this rotation happens in world space anyways.

There is clearly an algorithmic flaw here, but this is fairly complicated (and totally under-documented) code, not easy to follow...

You can still work around it by using edge and face mode?

I would like to work on this feature

Thanks for fixing it in such a short order.

Committed this in the menu rBd95dbd1f4f1c: UI: add kerning menu for 3D text editing since this is mostly a way to expose the key shortcuts, adjusting kerning with menu items isn't that handy.

Already got a good public-domain sample file for the initial work, thanks.

Go ahead, fire away!
Thanks for the help 🙂
I actually wanted some info regarding the issues related to the font. I'll try to come up with something.

In D6935#164827, @Nabil Adel (mywa880) wrote:

Sergey is rewriting Multires modifier in a local branch according to his weekly report . So you may want to submit the changes to each modifier separately?

Sergey is rewriting Multires modifier in a local branch according to his weekly report . So you may want to submit the changes to each modifier separately?

hi, thanks for the reply.
I still think this is a regression, from an artist standpoint there is no real benefit to have this new behavior, but I can see a number of cases where this behavior can cause problems:

Yes!! heck Yes!, Its a extremely welcome feature.

Use RNA directly for updating the handle types. This proved difficult because the points on the path didn't have a reference to the profile itself, which needs to be updated.

@Arvind R (r-arvind) - I am actually planning to apply for GSOC this summer , maybe I can take this up as my task

@Campbell Barton (campbellbarton) Any suggestions about my proposal to take this up for GSOC?

Prevent something around 99% of the edge from being off the screen.