On 02/22/2015 12:16 PM, Niemand Sonst wrote: > please post your branch, I will review it as much as it is in my > possibilities. > I can not understand, why it is not fixed, your suggestion is from 2013. > Seb, what happened?
Because nobody made time to review it. > One more question, related to: > -------------------------------------- > he whole thing is rather complicated by the fact that tool data is used > by realtime code, and realtime code can't access disk files. > -------------------------------------- > > Why realtime need to know about the tools? I'm no expert on this part of the code, Andy can probably answer this much better than i can. I think Motion has no knowledge of the tool table. I think it only uses tool offset information for a single tool: the currently active one, as determined by the interpreter. I think it gets this TLO information from Task in an emcmot message that's bounded in size and not involved in Andy's tool handling patch. I think the current tool table size limitation comes from a limit on the memory shared between IO and Task, where to tool table lives. I'd love to be educated if this understanding is wrong. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
