>
> I guess I mixed two issues - not loading unspecified components, and
> generalizing the POSTGUI_HALFILE scheme.
>
Ahh I though we weren't quite lined up :)
> > 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.
>
> uhm, thanks. Didnt think of that. In that case it should suffice to remove
> loading of unspecified components from linuxcnc.in.
>
> However, if that way of starting the UI is used, I dont yet see how
> linuxcnc.in knows to wait properly for the UI as per DISPLAY= to finish, as
> there wont be a 'DISPLAY=' in that case, and I dont see an obvious way to
> wait on 'HAL component suchandsuch unloaded'.
>
> let me try that out, maybe there some easy way
>
Yes while I should have said I load gscreen in the normal way and the AXIS with
loadusr.
If you don't have a 'DISPLAY=something' linuxcnc won't load but I don't know
the specifics why.
Could be just cause the script expects a name or as you alluded, linuxcnc needs
to know for
other reasons..
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
