#flex-dev Logs

Nov 13 2025

05:05 AM lcnc-relay: <AllAboutJake@> The first one throws errors cause I tried to move past limits not cause of the units
05:19 AM lcnc-relay: <AllAboutJake@> I did also confirm that Mach3 (not that I’m into that sort of thing) also updates the DRO based on g20/g21
05:55 AM JT-Cave: morning
06:38 AM rdtsc-w: They'rrrrrrre Great!
06:40 AM JT-Cave: Beignets!
07:36 AM lcnc-relay: <AllAboutJake@> JT, as I'm researching the M20/21 DRO thing, and on the subject of keeping the update() function fast, probably don't need to search the gcodes array for G2x to set "units_lb". Instead use "parent.status.program_units"
07:37 AM lcnc-relay: <AllAboutJake@> 'program_units': {1: 'CANON_UNITS_INCHES', 2: 'CANON_UNITS_MM', 3: 'CANON_UNITS_CM'},
07:37 AM lcnc-relay: <AllAboutJake@> Not sure how you set "CANON_UNITS_CM" though -- that's not a thing as far as I know.
07:41 AM lcnc-relay: <AllAboutJake@> Looking at the linuxcnc source, it seems like CANNON_UNITS_CM is kind of half-heartedly implemented, and _INCHES and _MM are where the action is
07:42 AM lcnc-relay: <AllAboutJake@> but probably should handle the case just for completeness.
07:47 AM JT-Cave: reading the nist documents it says CANNON_UNITS_CM is not coded
08:01 AM lcnc-relay: <AllAboutJake@> So reading up on how gmocappy is implemented -- it uses "hal_glib", which is an event-baed API to monitor the hal. (today I learned)
08:02 AM lcnc-relay: <AllAboutJake@> The code is constantly keeping the DRO values in both units and storing them in properties.
08:03 AM lcnc-relay: <AllAboutJake@> And when it receives a "metric-mode-changed" event from GSTAT, it toggles the DRO UI to show the proper units.
08:10 AM lcnc-relay: <AllAboutJake@> cmocaapy monitors the following events using GTAT callbacks rather than polling:
08:10 AM lcnc-relay: "all-homed", "not-all-homed", "hard-limits-tripped", "interp-idle", "interp-run", "line-changed", "metric-mode-changed", "mode-auto","mode-manual", "mode-mdi", "motion-mode-changed", "state-estop", "state-estop-reset", "state-on", "state-off", and "tool-in-spindle-changed"
08:10 AM lcnc-relay: <AllAboutJake@> *gmocaapy
08:27 AM lcnc-relay: <AllAboutJake@> PyDragon uses qtvcp's DRO widget which does the job of converting the units into the current "display units": https://github.com/rene-dev/linuxcnc/blob/40d2e8654c914331eebf8fcffb858ca5202a7c65/lib/python/qtvcp/widgets/dro_widget.py#L122
08:32 AM lcnc-relay: <AllAboutJake@> Sorry for all this. I think its obvious that this is the way I want the UI to work on _my machine_ -- but I also believe it is the correct way in general and would be best for flexGUI. At the very least, I don't think I'm in left field in wanting it. In the end, I can always maintain my own Fork.
08:32 AM lcnc-relay: <AllAboutJake@> I think the DRO and the plotter should both change their units in relation to G20/21
02:06 PM lcnc-relay: <AllAboutJake@> Love it when I can't figure out why a style sheet isn't aplying 🙂
02:08 PM JT-Shop: it has a mistake
02:09 PM lcnc-relay: <AllAboutJake@> yeah 🙂
02:10 PM lcnc-relay: <AllAboutJake@> computers do what you tell them--- not what you want 🙂
02:10 PM Tom_L: something is amuck with that last series of pushes
02:10 PM xxcoder: reminded me of that time I spent 4 hours to find bug of item->next being unset. added item->next = NULL; fixed it
02:11 PM xxcoder: hopefully yours isnt that hard to find bug lol
02:14 PM JT-Shop: ok
02:17 PM Tom_L: i put a G21 in a test program and switched between G20 & G21, the plot shows the G21 side shorter as it should but the dro displays inch
02:17 PM Tom_L: the dro in the plot
02:18 PM Tom_L: the flex dro doesn't change to mm either ( the one on my DRO tab)
03:10 PM lcnc-relay: <roguish> hello. well, raining now. up to 1.5 inches so far today.... that's a lot for us
03:11 PM Tom_L: are you near mud slides?
03:11 PM lcnc-relay: <roguish> nah.
03:11 PM lcnc-relay: <roguish> nor flooding
03:12 PM Tom_L: that and falling off into the ocean seems to be issues out there
03:12 PM * Tom_L goes for a nap
05:06 PM * Tom_L couldn't remember if he pushed a deb.. PR #397
05:06 PM JT-Shop: ok thanks
05:09 PM Tom_L: instead of making a metric config i think i'm gonna put a G21 in all the ops files and see what happens
05:09 PM Tom_L: then i won't have to debug all the number converisons to get a working config
05:09 PM JT-Shop: cool
05:10 PM Tom_L: i did that on the probe ones and that was ok
05:10 PM Tom_L: but
05:10 PM JT-Shop: I gotta use the gcode status so a change in the morning
05:10 PM Tom_L: the ops make calls to other subs. i think as long as i have G21 in all of them i'll be ok
05:11 PM Tom_L: that might be a weekend project
05:14 PM lcnc-relay: <AllAboutJake@> If you start in G20, does it put the state back to G20 after runhing the subroutine?
05:25 PM Tom_L: this is only for my testing
05:26 PM Tom_L: i have a full set of inch subroutines and did have a full set of metric but it got to be alot keeping them sorted out during testing so i abandoned metric for the time being
05:26 PM Tom_L: a week or so ago i tested all the metric probe routines
05:26 PM Tom_L: all that's left is the ops
05:27 PM Tom_L: there were 2 separate touch-probe3 ui files originally set up. one inch and the other metric and i didn't mix the two
05:28 PM Tom_L: now that i'm done putzing with tp3-touch for the time being i may get back to test the rest of those
07:06 PM lcnc-relay: <AllAboutJake@> I spent some time today trying to make arrow shaped buttons for jog controls. I think in the end just an image is the best way. The “setMask” function works but is not anti aliased so looks kind of bad