Gmoccapy - A new screen for linuxcnc

What you implement and what priorites you assign is totally up to you. I am just giving you a wish list :laugh:

If the 'back' button reloads the file most of my 'pain' regarding that issue is over. Didn't notice it does that. If I have to regenerate code using CAM then pushing file load->bla versus hitting a reload button is insignificant in extra time.

I am happy with the analog HAL pins since I am considering adding a few potmeters and rotary encoders for purposes like this. gmoccapy and touchscreen is great, but nothing beats a single-purpose knob.

A HAL-pin to switch modes: isn't it already there and named gmoccapy.v-button-2?

I will do a GIT pull today.

Regarding the encoder: I think I have your address in the mail somewhere. Originally we agreed that you would pay shipping, but let's consider that encoder a payment/gift for a wonderful piece of software. Sometimes it is also nice if you receive something back for all the hard work

If the 'back' button reloads the file most of my 'pain' regarding that issue is over. Didn't notice it does that. If I have to regenerate code using CAM then pushing file load->bla versus hitting a reload button is insignificant in extra time.

That is not correct! Not the back button do reload the file, but the save button does that! So the way to do your changes is, enter edit mode, change file, push save button (this will also reload the file!!!) and leave edit mode with the back button, check your changes and push start/run.
Have you noticed: The save button will also check the file for errors. Unfortunately it also do reload the file with that error Have to check on that one.

A HAL-pin to switch modes: isn't it already there and named gmoccapy.v-button-2?

You are right, they may be used for that purpose, as

• gmoccapy.v-button-2 => manual mode
• gmoccapy.v-button-3 => mdi mode
• gmoccapy.v-button-4 => auto mode

But IMHO that is not very obvious, as this are the hardware button connections, but it will work!

Regarding the encoder, just gave you an thank and more karma

Just a few thoughts,

1. The Save/reload/run button has always been on my list of imediate removal, but we trained the operators to not go near it.
Thank You for removing it

2. The rabbit~turtle selector, is it a selectable option via the settings or INI page? Or is it something we will have to look out for, and do some training on when I do my next update?

3. The M3/G96 issue, I haven't checked that out but am going to try that today as a work around of entering the M3/M4 first, hitting enter then entering the G96........ for CSS. Should be enough to not worry about if that works.

4. I see no reason that you couldn't remove the X=0, Y=0, Z=0 buttons. Our guys enter their own values, whether it is zero or not, just for their own piece of mind.

5. As for the addition of the error dialog when there are problems with arc start and end points being added, Thank You, our post proccessor has issues sometimes with this, and the guys stand there and scratch their ass for 20 mins until I walk by and tell their program is crap.

6. I was informed last week, never noticed it on my end, I don't run these things, just program them, that when you select the M1 button to turn it on, it doesn't turn yellow to signify that it is on, until you touch/select somewhere else on the screen.

Thanks Again for all the hard work Norbert,

Rick

4. I see no reason that you couldn't remove the X=0, Y=0, Z=0 buttons. Our guys enter their own values, whether it is zero or not, just for their own piece of mind.

Please DO NOT REMOVE these buttons as they are the most used buttons during touch off.

Consider that there are many folks that use the screen and that the common practise should be the prevailing practise in stead of special cases taking preference.

mariusl wrote:

4. I see no reason that you couldn't remove the X=0, Y=0, Z=0 buttons. Our guys enter their own values, whether it is zero or not, just for their own piece of mind.

Please DO NOT REMOVE these buttons as they are the most used buttons during touch off.

Consider that there are many folks that use the screen and that the common practise should be the prevailing practise in stead of special cases taking preference.

No Problem Marius,

Doesn't Make a difference one way or the other to me, I personally would rather have them use these buttons anyway, but I just build and program them, I don't have the authority to tell them how to run them.


Rick

2. The rabbit~turtle selector, is it a selectable option via the settings or INI page? Or is it something we will have to look out for, and do some training on when I do my next update?

Settings page, hardware tab! see screenshots some posts ago

6. I was informed last week, never noticed it on my end, I don't run these things, just program them, that when you select the M1 button to turn it on, it doesn't turn yellow to signify that it is on, until you touch/select somewhere else on the screen.

Very strange, as here it stays yellow, even if I change modes in between. Yellow means active, so finding an M1 will pause the machine. Any idea to make it more clear?

Please DO NOT REMOVE these buttons as they are the most used buttons during touch off.

Consider that there are many folks that use the screen and that the common practice should be the prevailing practice in stead of special cases taking preference.

Marius, you are right, we should think in most users, but I have an idea and need space on the button list, as I would like to integrate "macro workpiece aligning" Touch off the sheet with two touch on the side showing to you, one touch of on the left side and zero will be on the the edge and the rotation angle around Z axis is set automatically. If your workpiece is not witch an rectangular axis, you touch of two lines and the cut of the two lines will be zero and rotation is set for the first axis, or one circle and one line etc...

Would you be able to miss the Zero button to get that features? It is just one click more. For Plasma I am conwinced that the zero button are a very, very handy!

Norbert