Am 20.04.2012 um 13:40 schrieb Viesturs Lācis: > Michael, all the things You listed to be changed makes me think that > filter is much easier to do (except the math part).
For a single purpose-tool: probably yes, but then this fixes exactly your current problem and nothing else. I hinted at a fundamental architectural issue, which either can be kludged around as we go, or addressed. The suggestion I made wrt to the interpretation model addresses much more than the current topic. Some are: - unifying the line-oriented handling in task with the de-facto block structured rs274ngc language, leading to: - eradicating the convoluted MDI handling in task and interpreter, with its assorted stream of bugs. - substantially simplifying the remapping code, which is unnecessarily complicated due to this mismatch. - providing a common base for any 'global optimization on path segments', weeding out various ad-hoc structures here and there. - providing for a cleaner functional separation of the interpreter and canon layers than we currently have, which is a precondition IMV to any attempts about adding a new language front end if one were to do so. I'm not saying it's easy or it will fix your problem right away - I'm saying there are upsides to it long term. - Michael ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
