| Age | Commit message (Collapse) | Author |
|---|
|
Will print list of human-readable update flags, not the combined bitfield
printed as a number.
|
|
Common peeps! Why wasn't it already done?
|
|
Always check for non-Null pointers there! This versionning code is
called from many different places, with many different kind of Main's.
|
|
Was adding some relations twice. Harmless, but means extra stuff to do
when evaluating the scene.
|
|
While window manager is supposed to exist after file was fully read
and do-versioned, we can not rely on window manager to exist while
reading file and setting up an environment.
|
|
|
|
|
|
|
|
Was possible to miss some relations from being built
when parent object is linked to the scene graph indirectly.
|
|
Also don't align popover buttons with activated popovers.
|
|
|
|
Cursor can be a system one or drawn with OpenGL.
Before, dragging the transform manipulator would hide the cursor and reset it to the initial positon.
|
|
|
|
|
|
Timelines and Logic Editors are gone. So far they were simply replaced by broken
Info Editors, now they are replaced by Dopesheets in the new Timeline mode.
We reuse ScrArea.butspacetype to temporarily store the space-type identifier of
the deprecated editor (see 9db492de6dd07). That way we can identify it in
versioning code and replace it nicely.
Action editor creation needs a scene to set the scrolling based on frame range.
Active screen-layouts use the active scene of the window they are displayed in.
Inactive screens simply use the first scene in the main data base.
Note that inactive editors don't need version patching, readfile.c converts them
to SPACE_EMPTY already, so users can't activate them.
Files saved since the editors were removed will still be broken.
Workspace config files saved before this will also crash (will update default
one in followup commit).
|
|
The only real reason we need `butspacetype` is while switching areas, where we
need to delay the actual switch to the RNA _update callback since only there we
can access context.
So instead of trying to sync it with `spacetype`, only set while needed and
unset it afterwards (as in set to `SPACE_EMPTY`).
This should also allow us to re-use `butspacetype` in versioning code when
trying to read removed editors. It'll store the space type value of the removed
editor which we can then use on versioning.
For backwards compatibility, we store `butspacetype` with the value of
`spacetype`.
|
|
|
|
Note: Not bothering with doversion, re-using 280, 10 bump.
|
|
|
|
We bring back embossing however only for areas.
We use the same color for the corners.
|
|
|
|
|
|
|
|
We are using a different visual system to tell the areas apart.
There is no longer need for embossing.
|
|
Now that we can easily tell the corners apart, there is no need to
a specific action zone draw here (cursor still changes, naturally).
|
|
|
|
This makes easier to distinguish between different editors
(as oppose to an editor and its regions).
Note action zones look a bit strange with this. I recommend we do next:
* Make sure all 4 corners can be used as action zones.
* Remove their drawing code (or show them only on mouse hover).
|
|
Using extern makes too easy to get a crash if the original
function definition changed.
|
|
|
|
|
|
|
|
Match menu behavior
|
|
Also scale width with UI-scale.
|
|
- UILayout.popover(.. panel_type ..)
A single panel
- UILayout.popover_group(.. panel categories ..)
Expands all panels matching args.
Currently used in the topbar for redo and paint options.
|
|
- fixed the blending with solid drawtype
|
|
|
|
Also rename pupmenu -> popmenu
|
|
|
|
Originally added for icon drawing, no longer used.
|
|
Applied to newly added files in 2.8
|
|
D3165, D3166 by @ranjian0
|
|
|
|
D3161 by @JacquesLucke
|
|
Opening as in activating one in an area that didn't contain a properties editor
before.
|
|
Use software drawing, cache to an image at the requested pixel size.
|
|
|
|
|
|
|
|
Requiring context means we can't easily create new editors to replace deprecated
ones in versioning code.
Think it's reasonable to give editors access to scene and area data for their
initial setup though. They mostly need it for setting "the view", as in,
scrolling values.
Also did minor cleanup in top-bar creation function.
|
|
|
