I guess I'll send an email to the -developers list and ask what people think of branching 2.1.x
jepler: do you still have stuff planned that you want included before 2.1.0 ?
alex_joni: It's becoming clear that I don't have the motivation to do any of the lathe features (CSS and feed per revolution) that I thought I would.
alex_joni: there are some things that need to be added to the AXIS GUI, as you know
thought chris wanted to do that ;)
CSS and feed / rev
after he finished CNC'ing his own lathe, I borrowed the nist-lathe from him with the idea that I would work on some of those features
but it's just sitting downstairs, unused
I know how that goes :)
but as someone once said: "we gotta leave room for improvement"
I'd like to figure out how to make "halcmd newinst" work with "halcmd save"
I don't think that my "hallelujah" GUI will be ready for 2.1 (I also haven't touched it lately), but on the other hand it could easily live as a separate package for awhile, like AXIS did.
so basically I want to do minor stuff for 2.1
ok, I have the stuff I need to make work (optional stop and block delete)
my problem was. I asked at peters-cnc-ecke (german forum) if they werde satisfied with the german translation. The respone was that some people didnt know about it, because translation isnt clear working in the 2.0.x, as I found out, when I tried the life cd. Now I want to be sure it will work in 2.1.x (in head it works, so it will work in 2.1.x too) before I tell them something wrong
guess I never was motivated enough to test translation in 2.0.x
flo-h: one could make a localized LiveCD that has most/all of the stuff in german
mhh, I dont know really how, do you hav al link how this works?
I could walk you through the process sometimes
if you think that's a good idea
flo-h: most info is here: https://help.ubuntu.com/community/LiveCDCustomization/6.06
but it might appear a bit scary the first time ;)
it's "halb so wild"
thats nice, i have found http://uck.sourceforge.net/
"ich werde es versuchen"
uck might work too
although it's a pretty recent project
flo-h: I've done this a couple of times, so I know it can get problematic. if you get stuck drop me an email
thaks, if i need help i would ask you
flo-h: I'm also most of the time in here..
ok, so i know where to find you
also: if you have problems expressing yourself in english, you can use german in here (think the others won't mind it)
understanding english is not a problem, but sometimes i don't know how to write things
as I'm not a native speaker myself I know how it is
and my german should be better than my english
* alex_joni just had an revelating idea regarding optional stop
well, revelate us ;)
need to verify it first ;)
oh, verificalation is important
SWPadnos: it involves EMC_TASK_EXEC_WAITING_FOR_MOTION_AND_IO
ok, so you effectively insert a precondition for the move after an optional stop requiring the IO to be "off" (or some such)
isn't it the queueing that's an issue though?
it gets queued right
but it needs to flush the rest or such
hmm - I was thinking of the problem where motions after an optional stop may be queued, so flushing the queue moves past the stop point
if that's the problem - I may not understand it \\
don't worry.. no one does
ok, I'm in good company then ;)
it works !!!
optional block delete?
works properly that is :)
right - what you said :)
block delete is a bit harder to understand :)
jepler: still around?
[17:57:54] <alex_joni> http://pastebin.ca/219425
so we are talking m1? where there will be a switch to turn it on?
there is support in halui already
skunkman is now known as skunkworks