qtvcp issues

This morning I found that after the update pull that the text on the buttons are not changing from the "true_sate_string" and the "false_state_string". I only have two buttons that use this right now and the configuration on those still look good to me. I'm looking at the .py files occasionally to to see if I can figure out which file it is coded in to get a good under standing on how this is accomplished. It is not a high priority to resolve this right now.

My setting for those buttons are:
checkable = X
checked_state_text_option = X
true_state_string = MM
false_state_string = INCH

The other button: JOG BY STEP and JOG CONTINUOUS

Today I will try get started on linking the new gui into linuxcnc to allow me to see what pins show and which ones, if any need to be removed.

I do anticipate making some new widgets later on that will likely be just a bit different from the originals to help with touch screen use. There will likely also be some new ones.

I pushed a fix for that I think - at least it works for me - maybe you didn't get my last commit.
can you check if the last commit's title is 'oops...'
I like to use gitk to look at commit diffs.

Ok i will do that in a bit.

I thought that I would post a picture of the qtvcp gui that I have been working on for my Acra milling machine, I named it x1MillGui. It has four areas right now that uses stacked screens. It will take a while to make additions and changes until i'm satisfied with the layout.

The attached picture shows the present manual mode page.

I use this mill in manual mode a lot more that cnc mode and that shows up in the jogging section. There is a switch on the mills control panel that I built that disables the servo drives so that X, Y and Z can be moved manually. Z can be moved manually after releasing the clamp on the ball nut. A axis will stay under control of the gui. This mill also retains all of its normal none CNC functions.

This is what it show for my pull earlier this morning.

commit e51c7543dbc2124e0c51c42d2bfd76303dbf0957
Date: Mon Oct 15 21:39:10 2018 -0700
qtvcp -oops fix checkable action buttons state labels

I have not pulled again.

Yes that is the latest commit. can you check the qtdefault screen and see if the estop power and home buttons change labels?

Chris M

I used the Linuxcnc-Controller area (StatusStacked) and hoping that there would be no issues in getting some of my buttons to open up a particular page in a particular named stack by "stack name" and "index number".

If I need to I can change them to the QT Containers Stacked Widget type.

My stacked page names (changed from all being: ("statusstacked") are as below with each stack now starting at index 0.

stacked_frame_0
stacked_frame_1
stacked_frame_2
stacked_frame_3

Yes I think you'll need to change them. StatusStack widgets are specifically used to switch automatically to linuxcnc mode state.

I just pushed some more work on action buttons so they can run python code.
So if you want to switch a stackwidget or a tab widget with a button press...

add a default stackwidget and fill the pages as you like. name it something helpful - say stack_frame_0
add enough action buttons to cover all the pages you want to select.
select python_command_action on each action button.
under the false_python_cmd_string add this:
INSTANCE.stack_frame_0.setCurrentIndex(0)
but on each button use a different page index number. index start at zero and go up

That should do it.

Chris M

If you want to test this without changing the stack widgets you have you can.
It's just when linuxcnc changes mode they will change too.

Chris M

I changed my mind a bit and push more work that changes where the python commands are added. You'll find the python command properties under indicated_buttons title ( its still using action buttons)
Also for a non checkable button you's use the true_python_cmd_string now

Hope that wasn't too confusing...

Chris M