qtvcp issues

The error messages any more on loading with slider now. But the way the slider acts when resizing is a problem.

There is something amiss with the way the sliders act in relation to the orientation of the slider. I use vertical orientation and noticed that the ball goes off centre when width is adjusted, and also that the tick position likes to default to "above" position in the left panel label. When expanding the geometry the ball can go way off centre. The width adjust just effects the ticks and ball position not the slider or ball size.

Still talking about HAL sliders?
If you are they regular sliders with HAL pins - qtvcp does not change anything else.
I tried a panel with a slider it looks fine so it must be an interaction with something else.

If you can post your UI file or a sample ui file, then I could look further into it.
Chris M

Chris,

Here is a sample file in which the slider failed to keep things aligned after increasing its height. The expected action was to make the slider it self wider and keep thing in proper alignment. The slider may not be user friendly for use with a touch screen do to its size and is the reason I wanted to make it grow.

I have doing some debugging now while my gui is running and ran into a issue with the hal type of push buttons when they are used in the clicked(), clicked(bool) pressed(), released() mode with click() out. As long as the button is held down all if fine but as soon as the button is released linuxcnc terminates immediately with the below error. It does not matter how long the button is held down.

toggled(bool) toggle() button mode does not have this problem.

[QTvcp][INFO] postgui filename: x1Mill_postgui.hal (qtvcp:349)
/home/cnc/qt5vcp_py2/scripts/linuxcnc: line 880: 30737 Segmentation fault (core dumped) $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS

It looks like it is passing something that linuxcnc is not expecting.

Am I correct to assume that all the gui pins will not be available until a post gui file becomes active or are some available before then?

auto-mation-assist wrote: Chris,

Here is a sample file in which the slider failed to keep things aligned after increasing its height. The expected action was to make the slider it self wider and keep thing in proper alignment. The slider may not be user friendly for use with a touch screen do to its size and is the reason I wanted to make it grow.

Thank you for the test file, it made it easy to see the problem.
The problem is actually a QT problem - you can see it with a plain slider too.
If you change the ticks property to None or both, it looks fine.
This may be fixed in newer versions of Qt I haven't looked.

i'll add that status adjustment bars are more touch friendly, though I may need to do some work to make them more user friendly/versatile.

Chris M

auto-mation-assist wrote: I have doing some debugging now while my gui is running and ran into a issue with the hal type of push buttons when they are used in the clicked(), clicked(bool) pressed(), released() mode with click() out. As long as the button is held down all if fine but as soon as the button is released linuxcnc terminates immediately with the below error. It does not matter how long the button is held down.

toggled(bool) toggle() button mode does not have this problem.

[QTvcp][INFO] postgui filename: x1Mill_postgui.hal (qtvcp:349)
/home/cnc/qt5vcp_py2/scripts/linuxcnc: line 880: 30737 Segmentation fault (core dumped) $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS

It looks like it is passing something that linuxcnc is not expecting.

Am I correct to assume that all the gui pins will not be available until a post gui file becomes active or are some available before then?

So again this one is tougher because I can't get the same failure.
I can make a test panel that uses a hal push buttton that also has a clicked() signal to a slot in the handler file. - so it is possible.

If you are asking how to connect to screen pins from HAL files, yes the postgui file guarantees the pins are available.
Pretty much any other way might work but would be susceptible to race conditions.

Chris M