> > Considering the possibility of linuxcnc3 actually happening - wouldn't this
> > approach
> > be better there then changing things here?
>
> yes, but assume we start on linuxcnc3 - I dont expect it to have something
> working which can be released for months, if not a year or more
>
> meanwhile the folks trying to use HAL+GladeVCP only configs will continue to
> bang their heads against the wall, some dropping the idea of using such a
> setup altogether
>
I certainly am not wishing to lose people using hal + gladevcp only. I think
this is important to us in the long term.
Changing the script to load only specified components makes sense.
I must be missing something about POSTGUI though.
I am not seeing how POSTGUI as it stands limits the HAL+gladevcp only configs.
POSTGUI is for the cnc gui and why would you have a cnc gui if you are only
using HAL and gladvcp?
gladevcp has it's own way of making sure the HAL file is loaded in the right
sequence ..yes?
turning around ...
Why couldn't we load the gui with loadusr axis -<path to ini>
(This is a loaded question - I do this in a gscreen sample config to load
gscreen and AXIS)
if we add -W then HAL will wait till the gui is ready then you don't need a
POSTGUI file.
again I may be missing the point...
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-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
