> I am of the opinion (whilst accepting the validity of other opinions)
> that once you have a working configuration then you should completely
> stop using stepconf and make any further changes direct in the HAL and
> INI files.
>
> --
> atp
> If you can't fix it, you don't own it.
> http://www.ifixit.com/Manifesto
>
Andy you should qualify that with the point that you wouldn't use stepconf right
from the beginning ! :)
This is an old debate. While I agree ultimately it is better to learn linuxcnc
so you
can edit everything by your self, stepconf and pncconf should make it as easy
as
reasonable to NOT HAVE to do that while still making a config within what they
were designed for.
It easy for developers to forget the steep learning curve of linuxcnc and not
everyone wants to be an expert.
In this case stepconf did warn the user - unfortunately I guess it was not
quite clear
enough.
In 2.5's PNCconf what I did was have PNCconf load a 'jump file' which actually
just
loads other hal files. in this way custom_postgui is not ever used by PNCconf.
Though if it is not present it will create a blank file - just so it is easy
for a new user to
find.
It also copies backups in a backup folder with a time stamp added, so multiple
backups don't overwrite each other.
I'm not sure if this kind of complication is wanted in stepconf or not.
though the timestamped backups is pretty easy and would have saved you.
Chris M
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
