>
> Anything is possible, but I'd be very reluctant to go there. Currently
> all distances in HAL are in "machine units". Machine units are the
> units used in the ini file. Typically machine builders in metric places
> will use mm, and in inch places will use inches, but that is up to the
> builder. At the level where most HAL stuff takes place, changing units
> on the fly would be a disaster.
I tend to agree. Actually if AXIS had a pin such as:
display-metric-is-on
then I could do the conversion with a scale component
Or if AXIS had a pin that had X Y Z etc 'displayed value'
then I could use that directly (even better)
>
> Halui is a funny beast - it operates at a high level - the user
> interface. But it uses mechanisms designed for low level stuff - HAL.
> The intent of halui was to allow physical input and output devices like
> industrial oil-tite pushbuttons and indicator lamps to be used for
> operator input, so the low/high level connections make sense. But I
> think it is being stretched and twisted far beyond the original intent.
>
I think The reason is people want to change/add a few things display
wise and at the moment there is no way to get access to any of AXIS
internal data that controls that except thru HALUI.
> What is the problem you are trying to solve?
>
I want to display a pyvcp panel that shows a readout of what AXIS
displays in X Y Z.
halui.relative.pos is perfect right up till you switch AXIS to display
metric .
_________________________________________________________________
Keep in touch and up to date with friends and family. Make the connection now.
http://www.microsoft.com/windows/windowslive/
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
