Another plasma component...

Phill etal

Don't worry about the second screen for Gmoccapy. Everyone's install checks for it and no one has a second screen that I have seen. If one of the Python Gurus wants to get rid i of this on their install I am sure that commenting out the appropriate lines in the Gmoccapy Python handler file will cure it.

John

phillc54 wrote: It seems all your links are pointing back to themselves.
mkardasi had the same problem here

Do you have a recent version, if not then download the latest and try the configurator command I gave you earlier

Yes. pulled just now.

Ok I see what you're doing. The links that are created in the config directory are relative to the directory the configurator is called from. I called the configurator and 'upgraded' from both ~/ and ~/plasmac (my install directory). Neither of these worked. I finally just deleted the links and copied over the files directly and it's working now without links.

Yes, the configurator is run in the same directory the original plasmac source is.
When you do an upggrade you enter the inifile path/name of the configuration you want to upgrade.
The disadvantage of using actual file copies is that you need to recopy any files that have been upgraded whereas with links if they are pointing to the correct location then that is not necessary.

Cheers, Phill.

Any clue why mine aren't working? The paths that were created in my case were in the form of ./plasmac/configs/..., should they start with a ~ instead of a dot. Maybe it would be more bulletproof if the links used full paths?

I changed line #73 of configurator.py to
in order to get the links to use full path names and it seems to have worked. My new config loads just fine.

It is hard to give full paths because not everyone will put their clone into /home/{USERNAME}/linuxcnc-plasmac/

I have run the configurator from different paths that were real clones and have not had a problem. I have used both Stretch, Wheezy and LMDE2.

Cheers, Phill.