recursive make sucks
what are you building?
for so long, big projects barely built
well you know this
"Please consider using one of the 32 headers found in section 184.108.40.206 of the C++ standard."
"Surely 32 headers is enough for anyone!"
cradek: maybe this "flite" is worth a look, depending how far down the road you are with festival this time around
of course, you want the scheme interpreter, don't you..
yeah I even extended it
it's actually working, just taking a while
unlike the beagle, I think this'll actually work
jepler: I propose another fix for rdf0bdc9f4b7d: http://pastebin.ca/1816809
it's restoring previous behavoiur of Axis: when selecting background, rotation center will be at program center
and small remove of unused code: http://pastebin.ca/1816813
micges_work: it would be nice to be able to set the rotation center
(on some CAD programs I can do that by double-clicking middle)
alex_joni: it is easy in 2d mode, but how to get Z coord from perpective view?
heh it's easy too;)
see .. everything is easy if you know how to do it
micges: those are both OK to commit. Looks like they are only relevant on master.
guys, I've found scaling in a fanuc manual... G2/3 are still arcs, if R is supplied, then R is multiplied by max axis scale, if I-J-k is supplied, arc has min radius, and then linear move to the end is added.
it is possible to supply negative scale value -- it should mirror the output
I don't understand how that treatment of arcs under anisotropic scaling is likely to give useful results. Do you?
that is just sooo bogus: if I-J-k is supplied, arc has min radius, and then linear move to the end is added.
I can't see how that can help anything
the arc should become an ellipse arc if scaling is not uniform..
this is 0i manual -- quite antique... may be modern do it differently
Good morning jepler
bresenham algorithms are not useful for cnc, because they are not constant-velocity.
they proceed at one pixel per iteration, so the velocity varies from 1 to sqrt(2)
well.. they are for displaying the path
at trajectory level one could use NURBS directly
in alternate world crazy land where we use NURBS at the trajectory level
in alternate world crazy land where we have non-uniform scaling for XYZABCUVW
just so long as we get arcs in all the planes, such as XV, for our troubles.
A $375, less than a watt LED? http://mouser.com/ProductDetail/Osram-Opto-Semiconductor/OSP1G10WW2031C1000-3133-4Q9X/?qs=pD9e3CUnaqNF%252b64e83is7Q%3d%3d
alex_joni: you might still just stretch a circle arc... All the ellipses you get with non-uniform scaling are X-Y aligned.
if we introduce ellipses we'd better be able to get them with the major and minor axes not necessarily XY aligned..
and with the axes non-aligned as well
well, then we are better to transform everything to NURBS and work there... :)
that takes a bit more than just wishing it were so.
right... We are started with non-essential scale command, then added non-essential handling of G2/G3 in non-uniform scaling mode, and ended up with the need for handling non-axis alinged ellipses... Why stop half-way?
EMC: 03micges 07master * rcb6d75c06f7a 10/src/emc/usr_intf/axis/scripts/axis.py: Remove unused varables and minor redundant code
EMC: 03micges 07master * r8caaa7655a2d 10/lib/python/rs274/glcanon.py: Fix case when no vector was selected
jepler: is it hard to attach let say mandriva build for our buildbots?
(sim of course)
seb_kuzminsky: 11:14:14 <micges> jepler: is it hard to attach let say mandriva build for our buildbots?
[17:33:04] <aystarik> http://en.opensuse.org/Build_Service
-- could this one put to use?
at the risk of sounding like a broken record, all layers past interp/canon handle arbitrary arcs, and in fact you can currently get some by rotating XY and making a G18/G19 arc.
ries_ is now known as ries