Export key config outputting useless file #47567

Closed
opened 2016-02-25 23:30:40 +01:00 by Jeffrey · 7 comments

System Information
Linux x64

Blender Version
Broken: <= 2.68 (tested in release, master and octane's dist)

Short description of error
Exporting keymap to python file doesn't actually export the keymap.

Exact steps for others to reproduce the error
Export keymap from UP -> input -> "export key configuration..."
Open resulting python file in a text editor. The result is a single function with generic operation on data that doesn't exist. Attached is my resulting py.

There are no options in the export dialogue that may enable or disable certain options. I thought maybe it would export only expanded keymap categories, but expanding keymap categories and entries had no effect. Selecting a preset has no effect either. Factory startup output the same file.

It seems this function has been OOO for a very long time. "Remove Unused" in the node editor just got removed because it was non-functional, but I want to keep the ability to export keymaps into plain text. This has bothered me in the past when I have to reset my UP to pinpoint slowdowns, but have been unable to reimport.

ITA_hotkeys.py

**System Information** Linux x64 **Blender Version** Broken: <= 2.68 (tested in release, master and octane's dist) **Short description of error** Exporting keymap to python file doesn't actually export the keymap. **Exact steps for others to reproduce the error** Export keymap from UP -> input -> "export key configuration..." Open resulting python file in a text editor. The result is a single function with generic operation on data that doesn't exist. Attached is my resulting py. There are no options in the export dialogue that may enable or disable certain options. I thought maybe it would export only expanded keymap categories, but expanding keymap categories and entries had no effect. Selecting a preset has no effect either. Factory startup output the same file. It seems this function has been OOO for a very long time. "Remove Unused" in the node editor just got removed because it was non-functional, but I want to keep the ability to export keymaps into plain text. This has bothered me in the past when I have to reset my UP to pinpoint slowdowns, but have been unable to reimport. [ITA_hotkeys.py](https://archive.blender.org/developer/F285830/ITA_hotkeys.py)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @italic

Added subscriber: @italic
Author

I forgot to link in the original post, but the wiki also has a section about exporting/importing, but it's very brief doesn't describe much of anything.

https://www.blender.org/manual/preferences/input.html#export-import-key-configuration

I forgot to link in the original post, but the wiki also has a section about exporting/importing, but it's very brief doesn't describe much of anything. https://www.blender.org/manual/preferences/input.html#export-import-key-configuration

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2016-02-25 23:37:25 +01:00

Exported keymap is kind of a diff against current enabled keymap's default values. So if you did not change anything to current keymap, your exported keymap will be (nearly) empty…

Exported keymap is kind of a diff against current enabled keymap's default values. So if you did not change anything to current keymap, your exported keymap will be (nearly) empty…
Author

Perhaps it would be good to document such behavior, then. Addons register keys, but they are not exported, despite not being part of the defaults. It also seems that entire categories are exported if only one entry is changed. Overall this behavior is really misleading and poorly documented. I will try to set up docs locally to submit changes there.

Perhaps it would be good to document such behavior, then. Addons register keys, but they are not exported, despite not being part of the defaults. It also seems that entire categories are exported if only one entry is changed. Overall this behavior is really misleading and poorly documented. I will try to set up docs locally to submit changes there.
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#47567
No description provided.