Re download the latest build of 2.80 rc

Can you re download the release candidate.There were some bugs that were fixed

Can you provide a blend file that it is causes blender to crash.

Can you try the latest release blender 2.80 release candidate

In D5242#118758, @Harley Acheson (harley) wrote:

In D5242#118757, @Eitan (EitanSomething) wrote:

Affected tools is proper english

You are exactly right. But that particular combination reads a little funny.
"Affected tool" sounds like a person you wouldn't want to hang out with. Because "tool" can be an insult, usually someone with an overly-inflated ego. And "affected" can be pretentious, pompous, etc. So it works together quite well as an insult.
My own favorite is probably "Tools affected". It doesn't sounds clumsy like "Affect tools" and doesn't sounds like an insult.
Tools Affected: Move, Rotate, Scale.

In D5242#118701, @Harley Acheson (harley) wrote:

In D5242#118699, @Eitan (EitanSomething) wrote:

• Rename Affect Tools -> Affect tools

That seems quite nice and would have made sense enough for me to have looked at it correctly.
The words work. My earlier suggestion of "Affected tools" is a little funny as we don't typically use "affected" very much, more often heard as a sly insult.

I believe this was just fixed. Can you download blender 2.80 release candidate.

• Rename Affect Tools -> Affect tools

• Update space_view3d.py

In D5242#118693, @Harley Acheson (harley) wrote:

In D5242#118691, @Eitan (EitanSomething) wrote:

We could keep Move / Rotate /Scale and rename Affect to Affect Tool

Something like that would have kept me from making the mistake I did. Like "Affected Tool" or similar.

In D5242#118688, @Brecht Van Lommel (brecht) wrote:

Move / Rotate / Scale is the name of the tool it affects, I think we should keep those names the same since it's not really correct to say it affects all "movement" for example.

Small name change

• Move to Movement
• Rotate to Rotation
• Scale to Scaling

Where should I post changes that I made of this diff?

What is the status of this patch? People in devtalk are getting a little frustrated that this hasn’t been fixed.(not me)

This has been aligned at some point.

line 46 of the diff should be

Please do not set priority for the bug report, this is left for the developers. Waiting for developers to reproduce is for when a developer has claimed the task.

• rename MA_RAMP_COLOR_BURN to MA_RAMP_BURN to maintain MA_RAMP_ consistancy

• Replace COLOR_BRUN with BURN to avoid breaking python api

Changing from
{SEQ_TYPE_COLORBURN, "BURN", 0, "Color Burn", ""},
To
{SEQ_TYPE_COLORBURN, "COLOR_BURN", 0, "Color Burn", ""},
Is that something that can be done in 2.81?

In D5186#117731, @Harley Acheson (harley) wrote:

And I could be wrong, but think some of the changes in the enum lists (rna_material.c & rna_sequencer.c) could break python scripts. You might need to keep the second field the same as it is now to work with existing scripts. So in the change in rna_sequencer.c, 2794, might have to be:

{SEQ_TYPE_COLORBURN, "BURN", 0, "Color Burn", ""},

I don't really use Python in Blender so I could be wrong about this.

• Renaming

• Capitalization fix "Color burn" now "Color Burn"

• Capitalization fix "Color burn" now "Color Burn"

Clean up naming

Fix spelling mistakerna_sequencer.c at line 1460: "COLIORBURN" now "COLORBURN"

In 2.80 and 2.79b you can only export not import.Is exporting as DXF an option in 2.79b as well as 2.80?

Can you share your suggestions at https://devtalk.blender.org/t/blend-modes-naming-inconsistency/8006

Does it work with 2.79

Currently Import-Export AutoCAD DXF Format (.dxf) is being updated for 2.80. Quick question, is it an option at User Preferences > Add-on > Import-Export AutoCAD DXF format or just doesn't work?If it isn't showing up make sure the community tab is enabled.

When will this be added to blender ? are we waiting for 2.81

Removed extra parenthesizes.

Removed context from line 268 and replaced mosesfreestyle with Freestyle SVG Export

In D5127#116476, @Brendon Murphy (meta-androcto) wrote:

hi,
I am unsure of line 192 not using context and line 268 using context. Is there a reason for this?
The use of "mosesfreestyle" in the bl_location, surely this is an oversight?
Other than that this seems a very simple fix and most welcome.

Removed extra parenthesizes.

In D5086#116191, @Jacques Lucke (JacquesLucke) wrote:

@Eitan (EitanSomething) is there any discussion somewhere that says that this change is necessary? I'm fine with it, just wondering.

In D5080#115542, @Harley Acheson (harley) wrote:

@ronan ducluzeau (zeauro) wrote:
This proposal whithout last white pixel seems good to me. IMO, it is what makes it too big and perceived as too intrusive.

Actually that cursor has been described as both "too intrusive" and "too invisible" by different people. LOL. But looks like we are back to a previous cursor for a little while anyway.
But for completeness though, by "last pixel" you do mean the last outer white pixels, not the furthest inner ones right? The difference is basically if you want the gap in the middle to be larger. Removing one white pixel does make it nicely white-black balanced.
I still have a feeling we might eventually need a small selection of different cursors to select from for painting and sculpting. Otherwise I doubt we will find a nice balance that makes everyone happy.

In T65740#700253, @matc (matc) wrote:

I think he is referring to the offset between mouse cursor and scrollbar handle when zooming back in. The cursor reaches the left border before the scrollbar does. This forces you to move the handle multiple times to zoom all the way out.

What is supposed to happen to the scrollbars? Is it supposed to be delayed.

What are the specs of your system?

In D5036#114743, @William Reynish (billreynish) wrote:

@Antonio Vazquez (antoniov) Well yes, if you use a Cintiq/iPad Pro style device, you have no use for the cursor at all, so it really should be a general thing.
The main issue is, I suppose, that if you accidentally enable this option when using a mouse, your cursor will disappear and it will be hard to re-enable it if there is no cursor :)
Ideally I suppose we should make it smart, so that it could somehow detect the input device, although that may not always be possible.

The diff file isn't working.I'm getting the errors

It should be possible to adjust the dot or crosshair for tablet or mouse so the artist can customize its size to their preference.

What button are you pressing to get the Apply menu. When I right click I get the Object Context Menu

This isn't related to the custom hotkeys it happens with factory hotkeys.

I don't have a problem scaling the cylinder on the x axis.Can you try on the latest build.If it is still a bug can you share a video bug because I might being doing the scaling in a different way than you.

Can you attach a blend file

fix which files are included

Lower BMO_OP_MAX_SLOTS value to 21 from 22

Fix error when building soc-2019-bevel-profiles

• Update bmesh_operator_api.h