Qtvcp GUI and hal pins
10 Nov 2024 05:24 #314174
by Levi
Qtvcp GUI and hal pins was created by Levi
Im not quite understanding how hal pins are associated with a gui button. if i look a qtdragon is there a simple way to look at say the estop and see what pins are directly associated with it? Or in axis there is axisui.jog.increment pin and i can use this to make my mpg work by outputting the scale but i don't see anything like this in qtdragon. Would this pin have to be added in the qtdragon handler file like the other qtdagon specific pins? In 12.5.4 Build A Simple Clean-sheet Custom Screen stops short of giving examples of the pins. The widigits look to hove some pins as part of them, is the manual the only way to see, how does this end come together?
Can anyone give me some direction, Thanks.p { line-height: 115%; margin-bottom: 0.25cm; background: transparent }
Can anyone give me some direction, Thanks.p { line-height: 115%; margin-bottom: 0.25cm; background: transparent }
Please Log in or Create an account to join the conversation.
11 Nov 2024 02:10 #314224
by cmorley
Replied by cmorley on topic Qtvcp GUI and hal pins
Unfortunately I guess the short answer is no, there is not an easy way to see what pins the widgets create. I should try to add it to the docs I guess.
Qtdragon use the widget pins but also makes quite a few of it's own pins in the handler file.
A increments HAL pin would be a good pin to add to qtdragon.
Chris
Qtdragon use the widget pins but also makes quite a few of it's own pins in the handler file.
A increments HAL pin would be a good pin to add to qtdragon.
Chris
Please Log in or Create an account to join the conversation.
13 Nov 2024 04:49 #314364
by cmorley
Replied by cmorley on topic Qtvcp GUI and hal pins
If you are using master branch - I added jog increment pins:
qtdragon.jog-linear-increment
qtdragon.jog-angular-increment
qtdragon.jog-linear-increment
qtdragon.jog-angular-increment
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.224 seconds