cradek_ is now known as cradek
jepler: I wonder if the max length of the backplot is too long.
I'm not sure I've ever seen it undraw stuff, although I recall you added taht feature
yes but I made the buffer pretty big .. 100000 apparently
we either need to get our asses in gear, define what will be in 2.3 and finish those features; or we need to do something else like backport some features from TRUNK into a branch that we think are well-tested and separable
probably should be the former
I'm just realizing there is stuff on TRUNK that makes my life better -- but it's not in 2.2 because it's new features
I'm afraid the joints-axes stuff that I was talking about won't happen
I've got several machining projects that are absorbing my interest at the moment, so we shouldn't hold up 2.3 for stuff I said I'd do
this isn't intended as a call-out of anyone
I wonder what's broken in TRUNK
I should get a trunk checkout on the shoptask (if I don't already have one) and use it when I'm machining
that depends on your goals
I would recommend using a stable version for day-to-day work even if you're a developer
then I won't do _any_ testing
the only time I "test" is when I'm specifically looking for something
either testing a fix, or trying to reproduce a reported problem
(or testing a new feature)
well -- instead of doing that, I just spent 15 minutes backpoting two features in TRUNK I decided I wanted in 2.2
(the new no-popup operator messages and the less new unhome)
they don't involve any ini changes, right?
seems safe to me
well -- changing what happens when operator messages pop-up risks causing them to be lost, or causing worse user interaction problems than what we have now with the pop-up
"unhome" is likely to be lower impact
hmmmm what was I just talking about missing today?
cradek: you tell me
I would if I could remember
but you don't even use emc -- you just run boss all day
something for the HNC?
I've got to say that not having the pop-up makes the "insert drill XXX" and "start spindle" operator messages much less of a hassle
yeah I like that. I will test it too.
if you do "(MSG, do something idiot)" followed by M0, you can just hit resume once you've done whatever?
yeah -- you can clear the message whenever you feel like it
since it changes key bindings it's possibly messy
[23:48:17] <jepler> http://emergent.unpy.net/files/sandbox/notifications.png
if you missed it
"whenver you feel like it" includes never? (new message replaces old?)
they sort of "scroll up"
the box eats up more and more of the preview window?
or you just see the last few lines?
[23:49:59] <jepler> http://emergent.unpy.net/index.cgi-files/sandbox/multiple-notifications.png
the bottom one is the latest one
click "X" or press space to clear one, ctrl-space to clear all
I wonder if a black line (or rather, one pixel space) between them would help you understand that they are separate
some kind of border might clarify it
woo my spindle shipped
jepler: regarding debounce...
are you going right into an FPGA pin?