> 3. ALL guis, not just Axis, need to eventually learn how to start a
> POSTGUI_HALFILE if there is any chance itself or a subprocess creates
> additional HAL objects. To do so, they need to understand that they are the
> primary UI component. This suggests a per-ui command line flag like
> '--primary-ui'.
AXIS, TOUCHY and The future Gscreen all understand POST_GUI.
TOUCHY requires a touchy.hal file though.
It would be nice if linuxcncTK could be retrofitted with POSTGUI and at least
PYVCP panels.
but TCL is not my bag....
One thing that happens is if you try to load two guis in the same config (not
often to happen,
but sometimes when testing) is that both guis try to load the POSTGUI file and
of course the
last one fails due to the pins/signals already being present. Not sure if that
is a real deal breaker...
It would be a good idea is we added a section in the developers manual about
the common
requirements of a 'full featured' gui screen eg reparenting, POSTGUI etc.
easier to follow the standard then fix the code after the fact...
my 2 cents :)
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
