Skip to content

Conversation

@zz912
Copy link
Contributor

@zz912 zz912 commented Jan 15, 2026

I made documentation for:
GTK Verser Probe
GTK little Probe
GTK Mesa Tests

Copy link
Member

@hansu hansu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 👍

image::images/gtk_verser_probe.png["GTK Verser Probe",align="center"]

=== gtk_little_probe
This is old version from 2015. This older version has **less functionality**, but it **takes up less space on the screen**, which can be useful on smaller displays.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Less functionality compared to the original Verser Probe?
What's the problem with the original one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Less functionality compared to the original Verser Probe?

GTK Verser Probe is original Verser Probe too, but old.
LCNC had this old version for a long time, but it was unmaintained, broken, and undocumented. I did some maintenance and found that I liked this old version better than the new one.

GTK little Probe is only modification of GTK Verser Probe.

Less functionality is probably not an appropriate description.
It has sufficient functions for a workpiece probe.

What's the problem with the original one?

Size + useless functionality for toolseter https://vers.ge/en/touch-probes/35-tsm-v9.html + useless functionality for M6 + useless DRO

The new Versa Probe has no problems, I think a lot of people will be happy with it, but I think a lot of people will be happy with this old probe screen.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can see the version of Serguei Glavatski looks like the current official one - is that right?
And you created the tabbed version based on Serguei Glavatski's, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can see the version of Serguei Glavatski looks like the current official one - is that right?

I don't understand what you're asking me? Sorry for my english. Everything is from Serguei Glavatski.
We have in LCNC Probe Screen 2015

Here is actual version:
https://vers.ge/en/blog/useful-articles/probe-screen-v28
https://github.com/verser-git/probe_screen_v2.9
I tested actaul version. It works, but 2015 version is better for little size.

And you created the tabbed version based on Serguei Glavatski's, right?

I created the tabbed version based on Serguei Glavatski 2015.
I called it "Modification of Probe Screen application by Serguei Glavatski (c) 2015"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok I didn't know that the "official" version is also by Serguei Glavatski.
I pushed some changes to make it a bit more clear. I hope you agree with that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for changes.

@hansu hansu merged commit 772d5b8 into LinuxCNC:master Jan 16, 2026
14 checks passed
@zz912
Copy link
Contributor Author

zz912 commented Jan 18, 2026

How do I check the display of manuals for LinuxCNC?

This Manual shown in Visual Studio Code:
manual-visual_code

This Manual shown in Github:
manual-github

This Manual shown in web: :-(
manual-web

@hansu
Copy link
Member

hansu commented Jan 18, 2026

You have to build the docs locally to ensure the correct formatting. VS Code's preview uses the syntax of Asciidoctor but the Linuxcnc build system uses Asciidoc-py which has a slightly different syntax.

@zz912
Copy link
Contributor Author

zz912 commented Jan 18, 2026

You have to build the docs locally to ensure the correct formatting.

This is exactly what I want. I dont know how.

I don't know how to build it.
I don't know where it creates the built files.
I don't know how to open those files.

@hansu
Copy link
Member

hansu commented Jan 18, 2026

Formatting fixed with 6bbe877

This is exactly what I want. I don't know how.

https://linuxcnc.org/docs/html/code/building-linuxcnc.html#_building_for_run_in_place 😉

Just add --enable-build-documentation to configure.

I recommend adding --disable-build-documentation-translation (because it takes a lot of time) and also --enable-build-documentation=html saves you time if you skip building the PDF docs.

@zz912
Copy link
Contributor Author

zz912 commented Jan 18, 2026

Thank you for fix.

@andypugh
Copy link
Collaborator

How do I check the display of manuals for LinuxCNC?

The manual page on the web has updated now (it has to wait for the buildbot to finish, and only updates if everything, including all docs, build without errors.

https://linuxcnc.org/docs/devel/html/gui/gladevcp-panels.html

Seems to have been updated now.
"LinuxCNC version 2.10.0-pre0-5502-g11cf4dbe45 Documentation"
(I feel that it should be possible to go to that SHA in github but it doesn't seem to be a github hash.
But buildbot2.highlab.com has:
linuxcnc-doc-en_2.10.0~pre0.5502.g11cf4dbe45_all.deb | 2026-01-18 21:25 | 27M | )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants