You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a pythonless folks out there (and my boomer collegues) can you make an .exe version of the script, so it can be ctrl-v'ed to a disk and run without python or cmd involved, with only a path to .exe added at prusa postprocessing?
There is such an .exe for the preview gcode, and it saved A LOT of my staff from being braindead at the scaaary world of programming
For the sake of casual folks and greater end-user experience
The text was updated successfully, but these errors were encountered:
Getting something like that from a 3rd party is risky as you'll have no idea what someone has added to it; hence I won't post a link to an .exe. But until the dev does that themselves as a part of a release (or if they never do that, or if you don't want to have to trust them even then), you can take a look at https://pypi.org/project/auto-py-to-exe/ to generate an .exe for your colleagues yourself -- should just need one very slightly Python-savvy member to set this up for your team without such 3rd party risks.
Just tested it and seems to work well and was easy to convert. Resulting .exe is around 7MB. One note: executable upper/lower case matters. This is worth it for me as well to simplify the script trigger in Orca and avoiding the need for the complicated username-based Python path specification (it's just "c:\bin\fuzzyficator\Fuzzificator.exe" -run 1; for me now).
For a pythonless folks out there (and my boomer collegues) can you make an .exe version of the script, so it can be ctrl-v'ed to a disk and run without python or cmd involved, with only a path to .exe added at prusa postprocessing?
There is such an .exe for the preview gcode, and it saved A LOT of my staff from being braindead at the scaaary world of programming
For the sake of casual folks and greater end-user experience
The text was updated successfully, but these errors were encountered: