The Info view doesn't show every command (scripts) which I actioned. Example open new file, reload file, import, export...
How to show them?
$\begingroup$
$\endgroup$
4
-
$\begingroup$ Welcome to the site :) It would help us better understand what you want if you could add an example of a command which doesn't appear. $\endgroup$– gandalf3 ♦Oct 21, 2014 at 6:31
-
$\begingroup$ Are you looking for this: blender.stackexchange.com/questions/6817/… ? $\endgroup$– stackerOct 21, 2014 at 7:12
-
$\begingroup$ Sample in Maya, they show open file "file -f", import file "file -import", blender not show it i.imgur.com/7VT70ly.gif $\endgroup$– buonnguquaOct 21, 2014 at 7:26
-
$\begingroup$ Note that the commands shown in the info window are python calls. $\endgroup$– gandalf3 ♦Oct 22, 2014 at 7:00
Add a comment
|
1 Answer
$\begingroup$
$\endgroup$
8
While the info window can be helpful, the list of commands it shows is not a complete list, some operators are intentionally filtered out because they don't relate to editing your data (panning the view for example or scrolling the text window).
One example is renaming an object, changing the name in the 3Dview properties sidebar or object properties shows in the info window but renaming in the outliner doesn't show.
With opening/reloading blend files, the info window is cleared after opening a blend file, so the open command would be cleared out. If you refer to opening text files in python, any task using basic python functions isn't going to show in the info window, a call to a bpy based function would need to be made for blender to echo it into the info window.
EDIT:
You can see most if not all of the missing actions by setting
bpy.app.debug_wm = True
Note that this will give a lot of extra entries, including zooming, typing in the console, scrolling up and down....
-
$\begingroup$ In short: there is no way to record actions (macros), also see blender.org/documentation/blender_python_api_2_72_release/… $\endgroup$– CodeManXOct 22, 2014 at 10:41
-
2$\begingroup$ Actually
bpy.app.debug_wm = Trueadds most if not all of the missing actions. $\endgroup$– samblerOct 22, 2014 at 11:19 -
$\begingroup$ Definitely not all - e.g. doesn't show changing of properties. $\endgroup$ Oct 22, 2014 at 13:09
-
$\begingroup$ Custom data is not exposed at all. Operators which require it may still show up in the info area, but can't be executed again with the command shown. Window Manager operators will lack the proper context and can't be repeated either. $\endgroup$– CodeManXOct 22, 2014 at 17:13
-
1$\begingroup$ @GaryO The line to use would be
bpy.ops.import_scene.gltf(filepath="/path/to/infile.gltf", import_pack_images=True, import_shading='NORMALS'). $\endgroup$– samblerNov 25, 2019 at 9:50