Compiling Blender with closed panels in Factory settings #46969

Closed
opened 2015-12-14 09:53:19 +01:00 by Reiner Prokein · 6 comments

System Information
Operating system and graphics card

Windows 7 64 Bit
Nvidia 760 gtx

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)

Short description of error

Compiling Blender under Windows 7 with Cmake 3.3.0 and Visual Studio

Blender uses a startup.blend in the source code to create the factory settings. Theming settings like width and what tab is active gets recognized. Panel status open/closed not.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

I am not sure if this issue qualifies as a bug report since it is more relevant to developers. Users will not stumble across it directly. I nevertheless try it. With the hope that i get at least a hint.

One of the UI problems is the visual noise. Too much open at once.

Blender uses a startup.blend in the release/datafiles folder to create the factory settings. What is stored in this startup.blend will be the factory settings then.

When i use Blender as a user, and close all panels, like the ones in the Properties editor, and save the startup file, and when i restart Blender then, then those panels stays closed. So far so good. That's what the user can do. And here it works as intended. So the needed values are for sure available.

When i grab this created startup.blend file then, and use it to recompile Blender, and when i open the fresh compiled Blender version then, then the panels are as they were in the previous Blender factory settings. Open.

I would like to change this factory settings though. So that the factory settings already contains the closed panels.

All other UI settings gets compiled. Width of the panels, arrangement, etc. . But the panels stays open.

I cannot test if it works on Linux since i don't have Linux. Does it work on Linux? Is it a Windows 7 only problem? A settings problem with VS or CMake? Or is it a bug?

The first image shows the open tabs from the factory settings. The second image shows the closed tabs as i would love to have them in the factory settings too.

factorysettings1.jpg

factorysettings2.jpg

Kind regards

Reiner

**System Information** Operating system and graphics card Windows 7 64 Bit Nvidia 760 gtx **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional) **Short description of error** Compiling Blender under Windows 7 with Cmake 3.3.0 and Visual Studio Blender uses a startup.blend in the source code to create the factory settings. Theming settings like width and what tab is active gets recognized. Panel status open/closed not. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps I am not sure if this issue qualifies as a bug report since it is more relevant to developers. Users will not stumble across it directly. I nevertheless try it. With the hope that i get at least a hint. One of the UI problems is the visual noise. Too much open at once. Blender uses a startup.blend in the release/datafiles folder to create the factory settings. What is stored in this startup.blend will be the factory settings then. When i use Blender as a user, and close all panels, like the ones in the Properties editor, and save the startup file, and when i restart Blender then, then those panels stays closed. So far so good. That's what the user can do. And here it works as intended. So the needed values are for sure available. When i grab this created startup.blend file then, and use it to recompile Blender, and when i open the fresh compiled Blender version then, then the panels are as they were in the previous Blender factory settings. Open. I would like to change this factory settings though. So that the factory settings already contains the closed panels. All other UI settings gets compiled. Width of the panels, arrangement, etc. . But the panels stays open. I cannot test if it works on Linux since i don't have Linux. Does it work on Linux? Is it a Windows 7 only problem? A settings problem with VS or CMake? Or is it a bug? The first image shows the open tabs from the factory settings. The second image shows the closed tabs as i would love to have them in the factory settings too. ![factorysettings1.jpg](https://archive.blender.org/developer/F267972/factorysettings1.jpg) ![factorysettings2.jpg](https://archive.blender.org/developer/F267974/factorysettings2.jpg) Kind regards Reiner
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @tiles

Added subscriber: @tiles
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Julian Eisel self-assigned this 2015-12-14 13:27:52 +01:00
Member

No, this isn't a bug (well... for now).
The opened/closed state of a panel is read from .blends, but it's default state is defined when the panel is registered. See our API docs .

One more hint since I've seen your Bforartists tracker: The startup.blend in release/datafiles is not the only place to initialize factory/default settings. Git's method to handle binary files (such as .blends) is really memory hungry, so we try to avoid having to update such files for most cases.

No, this isn't a bug (well... for now). The opened/closed state of a panel is read from .blends, but it's default state is defined when the panel is registered. See our [API docs ](http://www.blender.org/api/blender_python_api_2_76_release/bpy.types.Panel.html#bpy.types.Panel.bl_options). One more hint since I've seen your Bforartists tracker: The startup.blend in release/datafiles is **not** the only place to initialize factory/default settings. Git's method to handle binary files (such as .blends) is really memory hungry, so we try to avoid having to update such files for most cases.
Author

Thanks Julian :)

Thanks Julian :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#46969
No description provided.