METRIC / SAE Indicator for pyVCP

More
29 Nov 2016 04:58 #83417 by Askjerry
The read-ahead shouldn't make much difference... it is more of a flag, it is more of a flag when in manual entry mode so you don't type G0 X10 expecting 10mm and get a surprise when it goes 10 inches instead.

When code is running... you are more or less just watching the show... it's when you are manually doing things... that's when it gets interesting.

Please Log in or Create an account to join the conversation.

More
29 Nov 2016 05:15 #83418 by cmorley
it can be important if you stop/abort a program and then restart in the middle.
I agree that metric/imperial settings are rarely changed in the middle of a program.

Chris M

Please Log in or Create an account to join the conversation.

More
29 Nov 2016 13:51 - 29 Nov 2016 13:52 #83431 by andypugh

for i in sorted(status.gcodes[1:]):
            if i == -1: continue
            if i % 10 == 0:
                if i == 210:
                    metric = True
                    break
                elif i == 200:
                    metric = False
                    break


Isn't this more Pythonic:
metric = True if 210 in s.gcodes else False
Last edit: 29 Nov 2016 13:52 by andypugh.

Please Log in or Create an account to join the conversation.

More
30 Nov 2016 01:20 #83466 by cmorley
yes it is.
My example came from code in gscreen which parses gcode for different reasons.
I was not trying for the best code, just an example.

Chris M

Please Log in or Create an account to join the conversation.

Time to create page: 0.087 seconds
Powered by Kunena Forum