Andy, I think there are two questions here:
1. Should the operator interact with the control in a way that mirrors the Fanuc implementation? This includes both Txxyy tool call and G10 P100xx offset setting, even if we suspect that it wouldn't break compatibility. It also includes a way of editing a table of geometry and wear offsets with sensible names (not in the 10,000+ range). 2. How do we store the data? I think that the answer to question 1 is yes, provided that either someone is willing to rewrite tooledit or create a Glade tool table widget. The answer to question 2 is open to debate, but I've not given it too much thought because of the talk about 0MQ replacing NML (and the tool table restructuring that would come along for the ride.) The only thing that I would advise is - don't couple the wear offset to the geometry offset. The entire scheme hinges on the ability to apply the wear offset from tool X to a different tool Y. Rogge ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
