User interface

Always get your machine working fully on axis first, then consider converting to a more modern interface. With say qrdragon, there are quite a lott of additional pins to connect to the GUI to enable every feature but you need to be confident the basics (from axis) are working... Be aware of screen size  limitations. I had to buy another monitor for QTD...

Just to follow on from Rod's comment.

Many of the UIs that are visually modern/graphical expect a 1080p display.  For example ProbeBasic imust have 1080p or larger.  The upside is a lot on a single screen at once. The more "original" or "old school" UIs expact much less with a 720p display being very roomy for them.

Re the comments on starting with Axis.  I would second that approach VERY strongly.   You will save youself a huge amount of potential frustration by having a working machine under Axis as your baseline.  That way when moving to another UI and you have issues you can better pin point where things are falling down when you KNOW you have a working Axis config.

For startup Axis is as solid as you can get, as soon as you want something more suited to your machine and work flow then Flex GUI is the best because you can have what ever you want and what ever screen size you want. Other GUI's you have to use what the programmer wants you to use.

JT

Well to be fair there is the included Qtvcp too.
You can build what ever you like with it.
Qtdragon uses Qtvcp.

What toolkit is best is probably subjective

Thanks everyone, I have taken rodw advice and starting out with Axis.

cmorley wrote:

Well to be fair there is the included Qtvcp too.
You can build what ever you like with it.
Qtdragon uses Qtvcp.

What toolkit is best is probably subjective
 

One of the big differences is Flex GUI uses PyQt6 while all the other PyQt gui's use PyQt5 which is at the end of it's life.

PyQt5 is based on Qt5 which was a cross-platform application framework used for building graphical user interfaces (GUIs) and other programs with C++. It was a major version of the Qt toolkit, but its support ended in May 2025

JT