Feature Request
CR has been pushed to 2.8 and master so you can switch back to either branch.
I will remove the test branch tomorrow.
They just grow up so fast!
Sounds good, I’ll switch back this evening. Been a pleasure testing this!
Please Log in or Create an account to join the conversation.
Thank you for testing. Your results were what I was hoping for.Sounds good, I’ll switch back this evening. Been a pleasure testing this!
I'm happy to test any time! What else do you have up your sleeve?
As far as issues I had jotted down that we never got to, I had:
- Unchecking Ohmic enable is really "ohmic ignore" rather than Ohmic disabled
- Wasn't sure where we ended up with locking out the MDI for Axis while a program (or GUI invoked cut) is running?
On that note, it could be confirmation bias, but it seems like there are a lot of issues specific to gmoccapy. It got me thinking, we had talked probably 6-8 months ago now about making a Plasmac specific GUI. Wonder if that's worth pursuing to get away from the Axis Vs Gmoccapy levels of support?
I know I had made a mock up based on PathPilot. I was a little disappointed to see Tormach's actual take on their Plasma screen for PathPilot. Maybe I'm biased but I think mine was better
Please Log in or Create an account to join the conversation.
I would like to see if I can get it to make a coffee prior to finishing a job.[I'm happy to test any time! What else do you have up your sleeve?
I don't remember these, I'll have a look tomorrow.As far as issues I had jotted down that we never got to, I had:
- Unchecking Ohmic enable is really "ohmic ignore" rather than Ohmic disabled
- Wasn't sure where we ended up with locking out the MDI for Axis while a program (or GUI invoked cut) is running?
Gmoccapy is very difficult to customise (about as difficult as I find it is to use). I was thinking about a GUI a few days back. Actually I was thinking about two of them, I would like to do a standard one for PC's and also one similar to Touchy for a Raspberry Pi4 so it would be able to use the standard Pi touch screen which is only 1024x600. I have been hanging back waiting to see what happens with the change to Python3, as that will have a bearing on which GUI toolkit to use.On that note, it could be confirmation bias, but it seems like there are a lot of issues specific to gmoccapy. It got me thinking, we had talked probably 6-8 months ago now about making a Plasmac specific GUI. Wonder if that's worth pursuing to get away from the Axis Vs Gmoccapy levels of support?
I agree, theirs looks pretty ordinary... but at least it is an integrated gui and the conversational looked interesting.I know I had made a mock up based on PathPilot. I was a little disappointed to see Tormach's actual take on their Plasma screen for PathPilot. Maybe I'm biased but I think mine was better
Please Log in or Create an account to join the conversation.
I think that's what happens when you type GO instead of G0I would like to see if I can get it to make a coffee prior to finishing a job.
They were peppered in with other bigger fish to fry. I figured they might have fallen off the radar.
I don't remember these, I'll have a look tomorrow.As far as issues I had jotted down that we never got to, I had:
- Unchecking Ohmic enable is really "ohmic ignore" rather than Ohmic disabled
- Wasn't sure where we ended up with locking out the MDI for Axis while a program (or GUI invoked cut) is running?
The prospect of being able to run stuff from a Raspberry Pi kind of blows my mind. Honestly Axis has grown on me, I don't find it nearly as cumbersome as I used to. Really I was thinking from a support standpoint it might be easier to just bite the bullet and move away from the other two. I definitely understand waiting on other things to be shored up though.Gmoccapy is very difficult to customise (about as difficult as I find it is to use). I was thinking about a GUI a few days back. Actually I was thinking about two of them, I would like to do a standard one for PC's and also one similar to Touchy for a Raspberry Pi4 so it would be able to use the standard Pi touch screen which is only 1024x600. I have been hanging back waiting to see what happens with the change to Python3, as that will have a bearing on which GUI toolkit to use.
Maybe when I write in today to report a bug or two I found over the weekend with the latest release of PathPilot, I'll add my .pdf of the mockup hahaI agree, theirs looks pretty ordinary... but at least it is an integrated gui and the conversational looked interesting.
I'm sure they'll appreciate that. Please Log in or Create an account to join the conversation.
