On 6 November 2012 13:08, Dave Caroline <dave.thearchiv...@gmail.com> wrote:
> That NML message restriction is just silly, just send a few tools per message, > those that are about to be used There is a further complication with the current scheme (and with your proposal) that means that several different "opinions" of the tool table values can exist at any one time in different parts of the code. By having each module extract the data from the database when required this problem is somewhat reduced. I suspect that it would be difficult for the code which transmits the tool table in the current structure to know which tools the requesting code wanted. Another inelegant feature of the current method is that it enforces a one-tool-per-pocket limit. I can conceive of a few scenarios where this is a limitation. (Gang tooling, and a rack changer with interchangeable racks, for example) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
