| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Changing from a loaded app-template back to Default (none set)
would scan paths for a file with no name. Harmless but silly.
|
|
|
|
|
|
|
|
|
|
Handle this in the operator
|
|
|
|
|
|
Useful for batch conversion and tests.
|
|
Conflicts:
source/blender/blenloader/intern/readfile.c
source/blender/windowmanager/intern/wm_window.c
|
|
Allow auto-execution to be enabled,
also move this to user-prefs versioning code.
|
|
|
|
|
|
This adds the ability to switch between different application-configurations
without interfering with Blender's normal operation.
This commit doesn't include any templates,
so its mostly to allow collaboration for the Blender 101 project
and other custom configurations.
Application templates can be installed & selected from the file menu.
Other details:
- The `bl_app_template_utils` module handles template activation
(similar to `addon_utils`).
- The `bl_app_override` module is a general module
to assist scripts overriding parts of Blender in reversible way.
See docs:
https://docs.blender.org/manual/en/dev/advanced/app_templates.html
See patch: D2565
|
|
This is already called by wm_init_userdef, in old code
different initialization methods were used but now it's not needed.
Confusing since prefs are loaded in this function that don't initialize temp.
|
|
Logic in this function is a bit scattered,
minor changes to avoid confusion.
Also rename 'from_memory' to 'use_factory_settings'.
|
|
No reason startup/prefs would ever be blend-file relative.
|
|
|
|
|
|
Conflicts:
source/blender/blenloader/intern/writefile.c
|
|
Previously it would always load into 'U' global.
Needed for loading & merging template preferences.
|
|
|
|
|
|
|
|
|
|
Internal change needed for template support.
Loading the user preferences first so it's possible
for preferences to control startup behavior.
In general it's useful to load preferences before data-files,
so we know security settings for eg.
|
|
|
|
Not user visible, needed for switching templates.
|
|
|
|
Print in cosole a warning when we skip autosave due to runnning modal op.
Related to T49974.
|
|
Obscure regression in own commit from b34929786.
While this could be considered correct, it introduces a crash so disable the update call.
|
|
|
|
Operator would call `WM_file_read()` directly whith G.main->name as filepath, which
gets freed whith main during new reading of file... Now use a local copy instead.
|
|
- BKE_blender_version.h (only version defines & versionstr).
- BKE_blender_copybuffer.h (currently only used for view3d copy/paste).
- BKE_blender_undo.h (global undo functions).
- BKE_blendfile.h (high level blend file read/write API).
|
|
dedicated source files.
This commit adds a new `wm_files_link.c` which contains everything related to append/link code,
moved from `wm_operators.c` (rather small currently, but will expand quite a bit with future reload & asset works).
It also moves all load/save .bland files (and related userpref/startup stuff) from `wm_operators.c`
to `wm_files.c` (some helper funcs were already there).
This also makes `wm_operators.c` significantly lighter.
|
|
option is disabled.
See rB935e241fa6ea095493 for details of the issue, but first fix caused regression T47632.
So for now handling the issue in a localized way, this is not a real solution (since this could happen
in other cases), but will do for 2.77.
This commit is to be backported to 2.77.
|
|
prefs.
Now store the multisample setting each window was created with.
|
|
So scripts can call Save-As without adjusting 'Recent Files'.
Uses same logic and file reading,
|
|
|
|
have it.
|
|
Use BPY_execute_* prefix for all Python execution commands
|
|
When load-ui was disabled, resetting factory settings kept existing UI too.
|
|
This brings back old (slower), higher quality method.
Useful since graphics cards often use a faster MSAA which only oversamples edges.
|
|
Reduce code-paths so improvements to 3D view render apply to sequencer too.
|
|
|
|
OpenGL sequencer render now uses a single fbo for all rendering.
|
|
WM_file_read must support background mode already
since it can be called by Python scripts in background mode.
|
|
|
|
Report an error instead of crashing if a new window can't be created
(typically caused by bad drivers).
|
