Post #4902: Thank you for the detailed explanation.
📋 Metadata
- Author: Pluglug
- Date: 2023-11-24 11:06:45
- Type:
bug_report - Quality Score: 8/10
- Reply to: post_04901
- Replies (1): post_04903
🏷️ Tags
v1-20-x popup-dialog toggle-side-area advanced unsolved
⚙️ Related PME Features
- Toggle Side-Area
- Popup Dialog Editor
- extra_operators
💬 Content
Thank you for the detailed explanation.
Toggle Side-Area
Toggle Side-Area is one of the features I had given up on in the past. I don’t fully understand the scope of the current problem, so I can’t fix it immediately. (Also, I’m short on time)
Upon revisiting the feature, I encountered the following two errors.
Operation: Creating a File Browser on the Left Side of the 3D View
Case 1: When there is no area on the left side of the 3D View (and a new area needs to be created)
Python: Traceback (most recent call last):
File "C:\Users\pluglug\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\pie_menu_editor\extra_operators.py", line 730, in execute
bpy.ops.screen.area_split(
File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py", line 106, in __call__
C_exec, C_undo = _BPyOpsSubModOp._parse_args(args)
File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py", line 60, in _parse_args
raise ValueError("1-2 args execution context is supported")
ValueError: 1-2 args execution context is supported
This error occurs when calling bpy.ops.screen.area_split. From the error message, it’s presumed that this function expects 1 or 2 arguments. However, in this code, multiple keyword arguments are passed, which is likely the cause of the error. There’s a high possibility that the arguments for bpy.ops.screen.area_split have changed due to Blender Python API updates.
Case 2: When there’s already an area on the left side of the 3D View. Most editors work but some errors occur.
Python: Traceback (most recent call last):
File "C:\Users\pluglug\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\pie_menu_editor\extra_operators.py", line 719, in execute
self.add_space(a, self.area)
File "C:\Users\pluglug\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\pie_menu_editor\extra_operators.py", line 578, in add_space
area.ui_type = space_type
TypeError: bpy_struct: item.attr = val: enum "FILE_BROWSER" not found in ('VIEW_3D', 'IMAGE_EDITOR', 'UV', 'CompositorNodeTree', 'Pencil4NodeTreeType', 'TextureNodeTree', 'ScriptingNodesTree', 'GeometryNodeTree', 'ShaderNodeTree', 'SEQUENCE_EDITOR', 'CLIP_EDITOR', 'DOPESHEET', 'TIMELINE', 'FCURVES', 'DRIVERS', 'NLA_EDITOR', 'TEXT_EDITOR', 'CONSOLE', 'INFO', 'OUTLINER', 'PROPERTIES', 'FILES', 'ASSETS', 'SPREADSHEET', 'PREFERENCES')
It’s a simple issue. space_type should be specified as FILES, but it’s incorrectly set as FILE_BROWSER. The method of obtaining items needs to be tracked and corrected.
These are the errors I’ve identified, but there’s a high probability that other problems may arise. If you find other errors, please report them along with the specific circumstances.
Hotkey
The hotkey issue might be more important for you. Therefore, I will put the Toggle Side-Area issue on hold for now.
However, I still don’t fully understand the situation. I would appreciate it if you could show me the situation through a screenshot.
Does “losing hotkey settings” mean they are “deleted” from Blender Preferences > Keymap?
Specifically, what gets deleted?
When PME writes to the keymap, it uses the operator wm.pme_user_pie_menu_call. Is this registered in the keymap with the title ‘Call Menu (PME)’? Can you find it?
ismailov.dima:
if you import them manually, they work. but this is not convenient because with each new start, these hotkeys have to be downloaded again, because they are not saved.
Does this mean you’re importing Blender’s keyconfig, or are you importing PME’s menu?
ismailov.dima:
and I noticed that when I install addons from Machin3, my hotkey settings get lost.
Specifically, how are they lost? Does everything disappear, or only a part (like Call Menu (PME))?
Also, you mention Machin3’s addon affects the keymap, but how does this relate to PME?
If you could provide specific steps to reproduce the issue, I can investigate in more detail.
Additional Note: Investigating the situation where the keymap is reset might be challenging, especially if you are currently working on a project. It could be quite bothersome. Therefore, it’s okay to conduct this investigation when you have time.
Also, Blender’s portable (zip) version is useful for this kind of troubleshooting. You can find and download the version of Blender you need as a zip file from the following site. (For you, blender-3.5.1-windows-x64.zip might be suitable)
Download Any Blender
Once you’ve downloaded and unzipped the file, create a config folder before launching Blender from inside it. If you downloaded version 3.5, the directory should look like this:
blender-3.5.1-windows-x64\blender-3.5.1-windows-x64\3.5\config
This allows you to have an independent settings environment.
Please launch Blender from the following directory:
blender-3.5.0-windows-x64\blender-3.5.0-windows-x64\blender.exe
image1206×972 192 KB