Developer Install for Probe Basic Py3 (For UI Development Only)

no worries, glad to have been able to help!

Tested and confirmed working on Armbian OS and Odroid N2+  (with 6 core ARM CPU)
Long way to go with Armbian yet, but this means this script should also work on the Pi and other CPU's supported by Debian.

Th Odroid PC is shown to the left of the keyboard

One problem to report and one stupid question.

Problem to report
After following up all the procedures, desktop "Probe Basic Mill" icon ended up errors on launching.
Based on debug messages, "probe_basic_postgui.hal" has three problematic lines about manual toolchange. I had to comment these three lines out to make it run. Error message is that port qtpyvcp_manualtoolchange.xxxx are not found.
----
# ---manual tool change signals---
#net tool-change-request => qtpyvcp_manualtoolchange.change
#net tool-change-confirmed <= qtpyvcp_manualtoolchange.changed
#net tool-number => qtpyvcp_manualtoolchange.number
----

Stupid question.
I used "Designer for PB Mill" desktop icon to change GUI.
Saved (closed and reopened to check whether it's really changed).
Ran updater.sh (checked probe_basic.ui => probe_basic_ui.py ... ok)
But running "Probe Basic Mill" icon on desktop still shows unmodified GUI.
What am I missing?

merongi wrote:

Stupid question.
I used "Designer for PB Mill" desktop icon to change GUI.
Saved (closed and reopened to check whether it's really changed).
Ran updater.sh (checked probe_basic.ui => probe_basic_ui.py ... ok)
But running "Probe Basic Mill" icon on desktop still shows unmodified GUI.
What am I missing?
 

Not stupid at all.

Assuming you just started editing the Probe Basic files that were installed on your computer, updater.sh (you can open it with a text pgm and see what it's doing) pulled the most recent files from the Probe Basic repository on GitHub and overwrote your changes.

If you make changes to the UI, you need to decide on a way to keep the changes from getting overwritten.  Some options:

1. Never update once you edit the UI
2. Save the UI file(s) in a different location, and then after updating compare the changes between the two sets of files and work out how to merge the modified vs. new files.
3. Make a fork or branch of Probe Basic on GitHub.  You can then edit your branch.  I think this allows you to review & merge differences easier, but I'm not really competent to walk you through the process.