- Amsterdam
-
Asset system (development lead), UI (developer & module coordindator), VR (initial development).
- Joined on
2013-12-12 -
-
The name suggests that this checks if the window has in fact global areas. What it actually checks if it should have them. Suggest WM_window_should_have_global_areas().
Not a big fan of naming this "CSD". I generally prefer avoiding abbreviations since they can be ambiguous (can mean different things depending on context). I also find that names can often be avoided and the intention/behavior can be described more directly, which makes the API more user friendly.
As @Harley noted in blender/blender!124258:
This issue is fairly obscure, hard to reproduce, easy to avoid, and would have existed a long time.
So setting to normal priority.
Closing this given the objection. Still nice to have some hint regarding the release notes there. But not worth keeping this PR open, we can always create a new one.
The PR [contributing page…
This does make sense to me, but would prefer if Campbell can have a look, since he understands possible implications more.
Issues for the UI module are more related to the UI system itself. The UI module doesn't maintain the Cycles/EEVEE UIs.
Checked with Sergey, he suggests assigning this to the EEVEE/Viewport…
Why is this assigned to the UI module? I'm not sure how that can help here.
