Wow. I thought it was actually broken by mistake/API changes, not purposely deleted. @Aaron Carlisle (Blendify) please communicate such things in the future, this is such an important feature missing for so long.

Hi! Thanks for the poke, I missed this one.

In D4123#93428, @Brecht Van Lommel (brecht) wrote:

@Pablo Vazquez (pablovazquez), what do you think?

So the last version is using TH_TEXT, and TH_VERTEX_SELECT when a vertex is active? Why not VERTEX and VERTEX_SELECT?

In rB454563ffac60856714247d39ceb294f5330463fd#208261, @Antonio Vazquez (antoniov) wrote:

@Charlie Jolly (charlie) If you can, please email me or contact by private message in twitter to provide you a link to a chat we have for discuss GP topics with all GP member teams.

In D4031#91247, @Mal Duffin (mal_cando) wrote:

It might be worth pushing the change temporarily to get some overall speed-up results from various VSE users, and revert if there are any issues.

Getting more VSE users to easily get access to the change and record before / after timings would be very useful ( there seems to currently be a good push with users, and some active developers able to put some time into making the changes ).

Can confirm that this fixed it also on XP-Pen Artist 15.6! Thanks!

@Brecht Van Lommel (brecht) @William Reynish (billreynish) Perhaps a way to prevent this in the future would be for right-click in corners/action zone not to spawn the Area Join/Split menu? It's not the user's fault if it's allowed to click there. About the Join operator, it could display a more helpful overlay message when the mouse is over areas that can't be joined (or even better, simply darken the non-available editors like in the image below). What do you think?

The select tool has changed from being a toggle between two operators to now always do only one task. A always selects everything. De-select is now set to Alt+A (as shown in menus). This gives a consistent way to select/deselect regardless if there was something selected or not.

Ah nice! Looks good to me too.

In D3982#90606, @Matej Junk (MJunk) wrote:

I would propose putting the render buttons on top to the right of scene and view layer buttons. It has the following advantages:

• better discoverability
• no matter which tab is active in the properties editor, the render buttons will always be visible - this helps a lot when tweaking a setting on the different tab then the output tab and rerendering multiple times to find the right value. This mitigates the need to click back and forth the tabs to find the render buttons.
• Currently in the Render Workspace - a dedicated workspace for rendering, there is no render button - which is weird especially for users new to Blender.
  
  Here is a quick mockup of the proposal: Render button group from left to right: Choose render engine, Choose to render preset, Render animation and render frame.
  

In rB3fdcd2293eadc277bc02297d4688a66f0456613b#206008, @Zino Guerr (Zino) wrote:

hey Pablo, it crashes aftwards.

Can confirm this is still happening in 2.80 Alpha.

Not my area but that discussion is from 2015, and your Blender Version says "2.76" which is over 3 years old.

In rB4c63ea2bc8e34741419d58890ac203d6393a001d#205813, @Campbell Barton (campbellbarton) wrote:

• If we want the current behavior to toggle back to the last non-wire shading mode (instead of solid), we could do that (personally think it would be nicer then whats there now).

I'm with @Brecht Van Lommel (brecht) here. I find the behaviour now after Campbell's commit more predictable, since X-Ray is decoupled and it stays turned on/off on Wire/Solid separately.

Thanks for looking into this @Eric Fode (ericfode) !

I fail to see why the need of a toggle (use_target_weight).