If you want to make it completely 3D compatible then defining angle in planar and angle perpendicular direction would have to be defined. This all could be taken relative to the working plane selected, if I am not mistaken, right? I propose making @P the perpendicular angle symbol.
something like: @ radius @P radius ^ distance so travel of @90 @P90 ^1.41421356 would go 1 unit of distance in axes X an Z, right? (actually, any two main axes, depending on the plane selected) On Tue, Dec 29, 2009 at 12:21 AM, Chris Radek <[email protected]> wrote: > On Sun, Dec 27, 2009 at 09:18:21PM -0600, Chris Radek wrote: > > > > With this scheme there are no modes, no new readouts, no new gcodes. > > In any place where you would normally specify X and/or Y, you can > > specify @R<T instead. > > I went ahead and incorporated this change today. I changed the > @R<T specification to @R^T because we use #<...> for named parameters. > > Even though it worked fine, I figured if I used (unmatched) < for > angles too, it would unnecessarily torture people who want to set up > their editors to colorify gcode. > > Chris > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers >
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
