Advanced Search

happy to help!  sorry for the hiccup!

Chris

yup, moved here, we are working on fixing the builder that updates the links!

nice! it is a wonderful thing to get true rpm working and have threading available! congrats!! post some picture too! show off your project!

Chris

2.9.3 works rock solid

Nice idea, but it still says "bad character"

blazini36 wrote:

Oh and is there any way to use a progress bar for something like spindle speed feedback? I don't see progressbar in the docs
 

I'll have to add a HAL QProgressBar... then you can connect it in your postgui.hal file.

JT

blazini36 wrote:

Can stuff like "view_dro_cb" be a pushbutton that is set to checkable rather than a checkbox?

 

You can now and no need to set it checkable in the designer the code does that for you.



JT

blazini36 wrote:

Is there any mechanism to use a qstackedwidget and some pushbuttons instead of the tab widget? I suppose you generally need to stuff some python in there to use the former.
 

So yes you can use a QStackedWidget now.



JT

How can i switch parallel to input mode?

Oh and is there any way to use a progress bar for something like spindle speed feedback? I don't see progressbar in the docs

JT wrote:

I have used a QStackedWidget before but not in this project and yes you need to code the buttons to change pages. I'm assuming you have a small monitor and the tabs from a QTabWidget take up too much space?

JT
 

Nah, it's a 16" touchscreen and a good portion of the controls will be in the hardware. I'm just not a huge fan of tab widgets, when the handles are large enough to be useable on a touchscreen they waste space, plus all of the handles are in 1 spot, vs pushbuttons that can be anywhere. I'm just getting rolling so they'll work for now.

Can stuff like "view_dro_cb" be a pushbutton that is set to checkable rather than a checkbox?

 

anyone update?

Does the pipe character create a new line?

I have used a QStackedWidget before but not in this project and yes you need to code the buttons to change pages. I'm assuming you have a small monitor and the tabs from a QTabWidget take up too much space?

JT

One solution would be to put those lines in a subroutine and insert the subroutine call into F-engrave.