before, the encoder direction was wrong
just thought I'd let you know
oh. that wouldn't help at all :)
hey! THANK YOU!
you're the only one who responded
anyway back to work..
ok, have fun
i'm noticing some problems with axis and recent changes: http://www.panix.com/~dgarrett/stuff/e.txt
np, maybe i'm doing something wrong
I doubt it, it's just that I thought I tested that returning inf from that function was OK
does changing all the INFINITY to 9e99 in gcodemodule.cc fix it for you?
seems like that change works on those tests, i originally saw it elsewhere so i should test some more things too
yes, i think changng INFINITY to 9e99 fixes all the cases i saw
EMC: 03jepler 07master * rf68caf7e35da 10/src/emc/usr_intf/axis/extensions/minigl.c: provide GLCALLxV for 5, 7 and 8 args
EMC: 03jepler 07master * rddafe687765c 10/src/emc/rs274ngc/gcodemodule.cc: fix crash loading empty file
EMC: 03jepler 07master * r326b73f9f5b4 10/lib/python/rs274/OpenGLTk.py: use swapbuffers method
EMC: 03jepler 07master * r96aab8b255f9 10/src/emc/usr_intf/axis/scripts/axis.py: don't define method; base class has it
thanks for the fix!
ries_ is now known as ries
e-jones is now known as jkastner|away
jkastner|away is now known as e-jones|away
e-jones|away is now known as e-jones
[Global Notice] Hi all. We just had a minor incident with an automated bot killing web gateway users as they connected. We've since disciplined it and things are back to normal. Sorry for the inconvenience and noise.
jepler_: if you are still wanting opinions, I think you should backport the new arc stuff and we'll hope for the best
unless I missed something on the mailing list, yours is the only opinion I've gotten
I figured you knew mine already...
I'll help you test if you do it
writing a new implementation is crazy
leaving it broken is distasteful
so far we've been really reponsive with quick bugfixes for serious things
so I'm in favour of backporting this, and a bugfix version or two if there's still something wrong uncovered later
jepler_: in commit r47459e45275 you disabled rotating origin axes according with s.rotation_xy, this was intended?
if so there will be no visible indication about current rotation, and I think that would be confusing if s.rotation_xy will be let say 1.5 degree
(or maybe I'm wrong)
with the tip of master the coordinate axes are shown rotated when displaying relative coordinates and not rotated when displaying machine coordinates
jepler_ is now known as jepler
at least, that's how it's supposed to be
I think a 1.5 degree rotation will be difficult to see no matter what
yes I've thinked about that after I wrote it :)
though I think there *is* a bug if you have zero offsets but do have a rotation..
yeah, in that specific case the rotation isn't shown
I had situation that preview was wrong when I entered g10 l2 p1 r30