-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to open Skeinforge settings from Pronterface #4
Comments
the problem is that it's looking for "skeinforge_application/skeinforge.py" while the file has been renamed to "skeinpypy.py" |
This is not fixed. Here is the error message: On my machine this file is located at "/Applications/SkeinPyPy/SkeinPyPy/skeinpypy.py" (note the additional SkeinPyPy). On my machine I have renamed the folder named "osx64-SkeinPyPy-NewUI-Beta4" that the build script creates to "SkeinPyPy" and placed it in /Applications, resulting in the path above. |
Fixed in a fork and sent pull request: daid/Printrun#1 |
Merged the pull request. It also contained the MacOS UI fix by BBum, but that's good :) The plan is to get rid of PrintRun anyhow (OMG?!?). I understand why it works stable, unlike some other solutions. And I have some "SkeinPyPy" like ideas for the interface. But this new printer control won't be done soon. So Pronterface is to stay for now. |
Whoops, still getting used to Git. I was intending to send a separate request for that one. Glad you were happy to integrate it. I like the idea of a SkeinPyPyified printing interface. |
Running a build from my fork (which is your fork merged with bbum's) I get the following error when selecting SkeinPyPy->Change Settings... in Pronterface:
/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python: can't open file '/Applications/SkeinPyPy/skeinforge_application/skeinforge.py': [Errno 2] No such file or directory
Since my application is located at "/Applications/osx64-SkeinPyPy-NewUI-Beta4" it looks like the path to Skeinforge may currently be absolute instead of relative.
The text was updated successfully, but these errors were encountered: