OpenGL swap call seems to hurt perfomance quite a bit? (@LazyDodo (LazyDodo) (LazyDodo) reports, didn't check myself)

I didn't even see that after searching for it! I'll close this in favor of yours, which seems to handle unit scale properly.

Use the existing function in draw_manager to draw text in 3D view.
We already have a patch that proposes to fix the same problem (D4325).
And the problem presented in patch D4379 needs to be resolved first.

@Brecht Van Lommel (brecht) during the period of the beta, we have had many reports like this. So I'm guessing that we should add some safe guards so that this doesn't happen (as it leads to crashing).

Here is a diff to apply on top of this revision.

My fault...MMB is already activated in the primitives to confirm, so there is a way to confirm already.

Yes, MMB could work... My concern is the wheel mouse is used for change some parameters, so it would be easy to make a confirmation by mistake.

To confirm without using the keyboard, keep in mind that MMB can be used.
Could this solve the problem? It's enough?

I assign to you. We can change it later if needed.

@Charlie Jolly (charlie) any idea here? is it possible to make a change on this for RC2?

In D5197#118853, @William Reynish (billreynish) wrote:

• Remember to address hiDPI too (2x). Even though the Windows world is far behind in desktop retina, it seems to be coming along.
• How do you plan to store these? Hopefully in a way that's more extensible so we can add many more cursors.

@Harley Acheson (harley) Interesting.

Nothing happen. Console without errors. And yes it was imported from old configuration file but still should work if this options are there or it shouldn't be imported.

Ok, I can reproduce the menu look by opening a 2.79 file and then doing File->Defaults->Save Startup File. All the existing Workspaces get added to the Add Workspace menu as shown here when you start Blender afterward:

Those look like the 2.79 Spaces which get converted to Workspaces when you open a 2.79 file in 2.80, but I've not seen them end up in the New Workspace menu like that before, so the question is how they got in there.

Might be working on 32-bit anti-aliased cursors for Windows... ;-)

Trying to get a handle on what parts felt funny to you. As far as I can tell the bare minimum highlighting we could do (besides none) is the following. Not in your face, and highlights the only state where an accident is destructive - changing multiples when your intent was to edit just one.

• Using OS-supplied cursors for area scroll X and Y
  • Using zoom cursor for area zoom
  • Added a new "comb" cursor (not hooked anywhere) for fun

There are a large number of in-betweens as well that are fairly logically consistent - which is why I added that blank template above.

@Brecht Van Lommel (brecht) : ...seems quite random that some buttons apply to all selected and some don't. Coloring the buttons is not enough...super confusing...

To help in experimenting with the design, here is a template that can be mocked up with how you might like indication to work. Three rows, showing a single object selection, multiple object selection, and multiple while holding ALT to indicate intention to edit only the active object. For each there are two properties, one that is capable of editing multiple and the other not. And for each showing regular, hover, and active states.

To help in experimenting with the design, here is a template that can be mocked up with how you might like indication to work. Three rows, showing a single object selection, multiple object selection, and multiple while holding ALT to indicate intention to edit only the active object. For each there are two properties, one that is capable of editing multiple and the other not. And for each showing regular, hover, and active states.

Volume at Sidebar --> Adjust --> Sound panel Should be displayed as 音量 in Chinese, but it is 体积 (the amount of space that some entity contains or occupies).

Just small tweaks to a few of the custom-drawn icons. Not enough to really notice though.

Possible (eventual) fix here:

Enum Lists (and popovers) share widget colors with menus (pulldown and popup). This can cause some problems when an enum list must pop up on top of a popover as you cannot tell where one starts and where the other begins.

The release notes that point to this task say:

This seems like it belongs in the paper cut thread and not the bug tracker:
https://devtalk.blender.org/c/user-feedback/paper-cuts

D is still used for annotate (although we could have an exception and override this).
W is used for context menu when select is set to right mouse select.

Put back in the ability to override the ghost cursors with custom-drawn, not just the other way around.

Thanks for the clarification on that detail @William Reynish (billreynish), that sounds sensible! Hopefully these changes are now agreeable for everyone. I understand the last minute changes going into the release candidates is for bug fixes so if this can't be slipped into RC2 then hopefully it can make an appearance for 2.81 in a few months!

Enable Viewport X-Ray -> Show Viewport X-Ray

Allows Mac to use native dragCopyCursor for GHOST_kStandardCursorCopy (dragging and drop)

Try that : https://developer.blender.org/T66252

I realized that reloading the factory settings doesn't save them into the user preferences. I thought that because it asked me something like »Do you really want to load factory settings?«^^
Okay, so what I have to do is checking every setting that differs from the factory settings. Maybe we'll find what causes this issue.

Alternative pencil cursor:

@Keavon Chambers (keavon) The word 'enable' is implicit in the fact that it is a toggle with a checkmark. The checkmark already communicates 'enable' or 'disable'. We put 'Show' in front of items to clarify that it is a display option.

Changes in this revision:

How is this still open after nine and a half years? And yes I checked, everything works fine.

• Alterations to pencil cursor
  • Allow system cursors to override custom cursors, not just other way around
  • Win32 - Using newer LoadImage in place of superseded LoadCursor in prep for other features later

Okay,
I reloaded the factory settings and it worked properly too. Than I enabled the addons

In D5104#118005, @Michael Soluyanov (crantisz) wrote:

I don't think that it is a perfect fix, because markers area still overlays first channel in VSE

I’m not sure if the new pencil icon. It just looks like a stick, and there is nothing pencily about it. Perhaps make it thicker and add a tip or other things that makes it readable.

Marker area covering the first channel is an unrelated issue. It happened in 2.79 too, and will be mitigated when we add the ability to hide markers per editor.

Property picker doesn't works too:

I don't think that it is a perfect fix, because markers area still overlays first channel in VSE

Tested and this is working properly.

Currently the "X" and "I" shortcuts for SculptDraw and Inflate & Blob are not working anymore

Only changes to "knife" cursor. Had some edges that were less than perfect.

Superceded by https://developer.blender.org/D5187

Other render operators behave the same way. So not a bug in the operator itself but how we handle the ESC keystroke. Not sure if we consider it working by design. @William Reynish (billreynish) @Brecht Van Lommel (brecht)

In T66562#715401, @Red Mser (RedMser) wrote:

(...)

• Press F3, press escape, the bake progress will say "Cancelling" then disappear

In T66562#715541, @Germano Cavalcante (mano-wii) wrote:

Why this insane resolution of Irradiance Volume Probe?
It took me about half an hour to bake this file.

Why this insane resolution of Irradiance Volume Probe?
It took me about half an hour to bake this file.
And I ended up not even being able to reproduce the bug.
Also this probe arrangement gives me no observable change in Eevee.

As per review by @Brecht Van Lommel (brecht), this update fills in missing bl_label for the two new added operators:

Design wise seems reasonable to me, but no time to review it right now.

In T66562#715398, @Germano Cavalcante (mano-wii) wrote:

It seems like a serious problem!
Please share a .blend file.

It seems like a serious problem!
Please share a .blend file.

Looks fine generally.

In D5197#117879, @Yevgeny Makarov (jenkm) wrote:

I mean, these cursors can be the same on both platforms:

Changes in this revision are just to which cursors are allowed to have colors reversed when viewed on Macs, based on input from Yevgeny and William.

Unless this is trivial to fix, I think b708917d94afa3a77be5e571b1c36a364d2ec6b5 should be reverted.