Feature Request

snowgoer540 wrote:

phillc54 wrote:

User Guide extract

Next I’ll have to learn the magic hidden text post trick lol

it is the icon to the right of spoiler (looks like a shield)

Edit: I used it accidently instead of spoiler...

CR has been pushed to 2.8 and master so you can switch back to either branch.
I will remove the test branch tomorrow.

phillc54 wrote:

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!

snowgoer540 wrote:

Sounds good, I’ll switch back this evening. Been a pleasure testing this!

Thank you for testing. Your results were what I was hoping for.

phillc54 wrote:

snowgoer540 wrote:

Sounds good, I’ll switch back this evening. Been a pleasure testing this!

Thank you for testing. Your results were what I was hoping for.

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:

1. Unchecking Ohmic enable is really "ohmic ignore" rather than Ohmic disabled
2. 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

snowgoer540 wrote:

[I'm happy to test any time! What else do you have up your sleeve?

I would like to see if I can get it to make a coffee prior to finishing a job.

As far as issues I had jotted down that we never got to, I had:

1. Unchecking Ohmic enable is really "ohmic ignore" rather than Ohmic disabled
2. Wasn't sure where we ended up with locking out the MDI for Axis while a program (or GUI invoked cut) is running?

I don't remember these, I'll have a look tomorrow.

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?

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.

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

I agree, theirs looks pretty ordinary... but at least it is an integrated gui and the conversational looked interesting.

phillc54 wrote:

I would like to see if I can get it to make a coffee prior to finishing a job.

I think that's what happens when you type GO instead of G0

As far as issues I had jotted down that we never got to, I had:

1. Unchecking Ohmic enable is really "ohmic ignore" rather than Ohmic disabled
2. Wasn't sure where we ended up with locking out the MDI for Axis while a program (or GUI invoked cut) is running?

I don't remember these, I'll have a look tomorrow.

They were peppered in with other bigger fish to fry. I figured they might have fallen off the radar.

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.

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.

I agree, theirs looks pretty ordinary... but at least it is an integrated gui and the conversational looked interesting.

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 haha I'm sure they'll appreciate that.

rodw wrote:

I have to agree Plasmac needs its own Touch screen GUI but it really needs to have a 1920 x 1080. I think it needs a really flat interface with running code, jogging and MDI all on the front screen, not like Gmocappy swapping tabs all the time!

Bu then there are (expensive) industrial monitors like this one at 1280 x 800 so it will be hard to please everybody (but it does support 1920 x 1080)
www.xenarc.com/1219GNS-12.1-inch-sunligh...di-video-output.html

It is surprising how quickly you run out of real estate when you try to have a lot of info on the main screen. To my mind it is unfortunate that LinuxCNC users seem to want to waste so much of the screen with the preview.