GUI for PlasmaC - QtPlasmac

tommylight wrote: Touch screen friendly = yes !
As simple as possible main screen = yes !
...
Hence a nice touchscreen with a simple GUI would be nice.
Just thinking out loud....

I like simple as well Tom, I really want the minimum amount of widgets on the main screen as possible.

I think I need to stop playing around with the stylesheets (I tend to get sidetracked with something new) and try to work out a decent layout then we can add the bells and whistles later...

phillc54 wrote: (I tend to get sidetracked with something new)

That tends to happen a lot !

rodw wrote: The immediate problem with that is that it drops you out of the nice touch screen interface. But hey, that can be the last thing tackled.
Parsing a calculator string is a perfect example where recursive programming is required.
When I googled "python calculator parser" this link popped up.
gist.github.com/urielha/6c11c29073dddbb9a0b9a1b92c1af3be
Not saying its a good one but it looks like it covers the basics. Just define variables for x,y, z etc that return the current DRO positions.

Qtvcp has a calculator dialog available. To get it to show:
in the screenoptions widget find and click the checkbox property for 'calulator_dialog_option'
Then on the axisToolButton widgets look at the property 'dialog_code_string' - change it from 'ENTRY' TO 'CALCULATOR'
Bingo

Chris

The nice that is in the entry but not the calculator is you can use axis letter to represent the current position of axis for calculation.

again IIRC there is a possible popup screen keyboard available - it's ugly and annoying if you don't need it but of course could be improved.
In QtDefault it pops up for MDI if you want to see it.

Chris

Blender has the calculator set up for axistoolbuttons if you wish to see what available.

Thanks Chris, I will check that out tomorrow.

Should I put these UI and handler files in share/QtVCP/screens or in the PlasmaC config directory.