Skip to content

Conversation

@John-Hackett
Copy link

Adding a check for to determine whether Blender is running through the command line or through the GUI. Lets users debug Blender when its running in a pipeline or any tests they've written for their addon

John Hackett and others added 3 commits May 6, 2022 09:31
Adding a check for to determine whether Blender is running through the command line or through the GUI. Lets users debug Blender when its running in a pipeline or any tests they've written for their addon
@AlansCodeLog
Copy link
Owner

Hi, great idea!

Minor nitpick, argument should probably just be named waitForClient since it is not actually limited to being used in background mode. That specific use case could be mentioned in the readme.

If you could add something to the readme with a small example that would be great. Otherwise I'll do it but I might take a while. After "Debugging/Editing Scripts" would be good. It would also be nice to mention you can use bpy.app.background to check if blender is running in background mode.

Version number also needs to be bumped to 2.1.0 before merge.

@John-Hackett
Copy link
Author

Great suggestions, I'll update for those

@John-Hackett
Copy link
Author

I think this is good to go now, Let me know if there's anything else that should be changed

@John-Hackett
Copy link
Author

Ran into a corner case and wanted to update it, now its good to go

@AlansCodeLog
Copy link
Owner

Okay, will take a look at this this weekend if I can.

@AlansCodeLog
Copy link
Owner

I did not end up liking the idea of the addon automatically assuming 'waitForClient` when blender is running headless, but I have added instructions for how to accomplish this from an addon or script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants