#linuxcnc-devel Logs

Jun 22 2018

11:17 AM seb_kuzminsky: rob ellenberg tells me he thinks he has a fix for #447 that he's going to dust off and polish up
11:20 AM seb_kuzminsky: that dude is amazing
11:46 AM pcw_home: Yay Rob!
11:47 AM pcw_home: Yay Seb for testing/plotting the issue!
02:54 PM andypugh: That’s interesting, and annoying
02:55 PM andypugh: I just compiled the latest Master on my lathe, adding absolute resolver support based on position.txt
02:56 PM andypugh: And my lathe macros don’t work in Touchy any more. They did work in the previous version, one of the external offsets branches.
02:57 PM andypugh: I _think_ it is because cycle-start is used both by the Glade handler and the main Touchy interface.
02:57 PM andypugh: Touchy seems to be trying to run the G-code programme even if the Auto tab isn’t frontmost…
03:01 PM andypugh: https://pastebin.ubuntu.com/p/MQJdfk7frm/
03:01 PM andypugh: If anyone is interested
03:59 PM andypugh: So…
04:00 PM andypugh: I have added an output pin from the GladeVCP panel and then HAL uses that to divert the cycle-start either to the panel or to the main touchy.cycle start. I probably should hav done this from the staert, and it is a partial solution.
04:05 PM andypugh: In this sense od “partial solution” https://goo.gl/images/578R3e
04:06 PM andypugh: What seems to have changed is thebehaviour that re-enables MDI buttons in GladeVCP
04:07 PM andypugh: Because my python handler runs the macros by emitting a “click” on a GladeVCP MDI button this means that my macros only work once, after LinuxCNC start.
04:08 PM andypugh: This might actually be the result of a bug-fix.
04:10 PM andypugh: I wonder if GladeVCP MDI-button widgets should be active in MDI mode? Or manual mode? Or both?
04:19 PM andypugh: No. That doesn’t seem to be it.
04:20 PM andypugh: (I do get the feeling I am talking to myself)
04:20 PM Tom_L: naw, just can't be of any help :/
04:54 PM seb_kuzminsky: i don't use either of those things and i don't have anything helpful to add