rem em ber - in Document QTvcp Development 5.6. Dialogs

QTvcp Development

5.6. Dialogs
Dialogs (AKA pop up windows) are placed on the screen in Designer.
It doesn’t matter where on the layout but to make them hidden,
cycle the state property to true then false.
By default, if there is a preference file, the dialogs will
rem em ber their last size/placement. It is possible to override
this so they open in the same location each time.

remember

so many thanks to everybody doing all the great work, I love to use LinuxCNC all the time - many thanks

Thanks fixed in 2.8

Chris M

Thanks, I hope it is ok to put some news in here? Found

2. INFO
IINFO is a library to collect and filters data from the INI file.

The available data and defaults:


INFO

www.linuxcnc.org/docs/devel/html/gui/qtvcp_libraries.html
i think the tread is referring on this documentation

in the User interfaces there is no QTpyvcp interface on this time
is it just a screen over gscreen i guess
or will it be a own interface at one time

Hi pl7i92 sorry - reading and studying a lot of QtPyVCP documents at this time, I only found some spelling to be corrected, I hope it is ok to put this here in some reply?

in Documents 2.8 - QTvcp Lybrary modules

2. INFO
IINFO is a library to collect and filters data from the INI file.

IINFO spelling should be corrected to INFO

pl7i92 wrote:

www.linuxcnc.org/docs/devel/html/gui/qtvcp_libraries.html
i think the tread is referring on this documentation

in the User interfaces there is no QTpyvcp interface on this time
is it just a screen over gscreen i guess
or will it be a own interface at one time

QtPyVCP and Qtvcp are two different projects.
Qtvcp is included in linuxcnc - QtPyVCP is a separate project, to be used with linuxcnc.

There are several experimental Qtvcp screen samples included so far:
linuxcnc.org/docs/devel/html/gui/qtvcp.html
They surely need polish - I build them to test building/programming ideas.
I'm not great at building pretty screens but I find - in time people give back great screens to the project.
(or this seems to be the case with Gscreen - also my project)

Qtvcp is separate from Gscreen but it's building/programming principles are similar.


any feedback - or code or spelling corrections is fine to post here.
(In the case of substantial code - a GIT patch or github pull request in nicer for me)
Thanks

Chris M

Surely this could be done - the tool offsets and user offsets page seem similar to what you are describing:


How do you currently enter the data?

Chris M