The “module object has no attribute…” or “no module named…” kind of messages come from the fact that python can’t find the library. This may be a local problem on your end - here I just downloaded the latest version and scripts are working.
In the script editor, do the paths to the libraries exist and are they correct?
Thanks for a quick reply, Mitch!
What you say makes sense and I’ll have to check on my RH6 PC later today.
The thing is, I’ve run the AutoCPlane script at startup for a long time now without problems - it’s just with the latest update that this is no longer working. So in that case the WIP installer messed something up with its paths. You are not having out-of-the-box problems with the latest WIP?
OK, testing further, I am not having problems with most scripts, but I did find one set of stuff that is not working - anything that involves using an open or save file dialog (via rs.OpenFileName or SaveFileName) :
‘OpenFileDialog’ object has no attribute ‘ShowDialog’
‘SaveFileDialog’ object has no attribute ‘ShowDialog’
I have not tested other stuff extensively, the scripts you mentioned above seem to work…
Yeah, and I just installed the latest on another laptop (Win8 as opposed to Win7) and when I start that, Rhino crashes right away. I’ll go into safe mode to delete the automatic start-up of this script…
I know how to get rid of the start-up error but I’ve been keeping it there as a reminder of functionality that I would like to continue to be there.
That sounds good!
I guess it’s all in the “may”
I’ll have to check it when I get a chance but that sounds like it behaves like the latest version of that script and not an earlier prototype that - to me - was the right way of implementing that functionality.