KeyError vtk_backplot

hi,

i'm not sure if this is a bug or not.. I'm using the devolper version and even re installed it. 

When changing the WCS to another than G54 directly after referencing the machine, i will get a backplot error when loading a nc program. I use the example ones "3D_CHIPS.ngs and THREADING.ngc..

File: vtk_backplot.py line 767, in load_program
point_01_pos = self.path_offset_start_point[prev_wcs_index]

it happens here:
            LOG.debug("

---

length(path_actors): {}".format(len(self.path_actors)))
            if len(self.path_actors) > 1:
                # Load the start point of rapid from the next offset paths
                LOG.error(f"prev_wcs_index {prev_wcs_index} not found in path_offset_start_point")
                point_01_pos = self.path_offset_start_point[prev_wcs_index]

out:
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][DEBUG] 

---

wcs_index: 1 (vtk_backplot.py:705)
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][DEBUG] 

---

current_offsets: [50.0, 50.0, 0.0, 0.0, 0.0, 0.0] (vtk_backplot.py:709)
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][DEBUG] 

---

current_position: 50.0 (vtk_backplot.py:750)
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][DEBUG] 

---

length(path_actors): 2 (vtk_backplot.py:766)
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][ERROR]  prev_wcs_index 0 not found in path_offset_start_point (vtk_backplot.py:769)
[qtpyvcp.app.launcher][CRITICAL]  Unhandled exception in vtk_backplot.py line 770 (launcher.py:37)

Seems that this code was changed two months ago.. 

I  just found out that there should be a blank.ngc loaded on startup for initialisation. So i added a ngc file with:
(New Program)

M30

and loaded it as default, but that will directly throw an error on startup:File
"/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py", line 767, in load_programpoint_01_pos = self.path_offset_start_point[prev_wcs_index]
 

i don't get that on the latest release so its difficult to say what is causing it on your setup unfortunately, could be a yaml setting perhaps, that is where i would start looking first.

I'm sorry for the confusion it seems to be regarding the dev version. If i change to stable everything works.

But this leads to antother dumb question.. If i change to stable by using the apt manager probe_basic_mill_designer will use the normal src and not the venv (It starts with the normal UI and not the one in dev/probe_basic/src). As soon as i uninstall probe basic and qtpyvcp via dpkg it works again.. But if i would build a .deb file out of my changes i guess that i will also have all the bugs which are not fixed so far from the dev version.. Is there a way to run the designer launcher on the stable version?

Mh if i delete qtpyvcp from my dev/ folder its working.. So i guess the installer uses the non stable version? 

Ok i just added a git tag of qtpyvcp to 4.0 in the installer to manually choose the versions of QtPyvcp and probe-basic for my venv the git tag in the installer and now everything is working. At least its not throwing an error, but the plotter seems to have an issue with drawing the preview where it should be when changing the WCS

dev and apt/deb should not be installed on the same pc, that is not the intended use case, the script installed dev install is meant for doing development work for the software and apt/deb is designed for machine use on a stand alone system.

the confusion i think is between stable and develop version which is simply which branch the update pulls from. stable being a locked down version and develop being the version currently getting updates and changing.

the dev install is seperate altogether and is meant to be able to switch between branches, add branches for new features and testing and merge into the devlop "main" branch, which then gets distributed via the apt update on machine pc's.

it is an error to have apt/deb installed on the same pc as the script installed dev installation, it will cause conflicts. you would then have two files sytems, one installed at root level and one installed at user level which is run in a venv.

it is terribly confusing and frustration even for us, we previously were noot forced to use the venv on pip installs which allowed for all of the dependencies and the required software to be installed at a root with the src folders readily available for editing at the user level, but this changed in debian 12 unfortunately orcing us to create the venv for those who would be setting up dev and using git to pull/push branches for work on the project.

i uninstalled all apt/deb while using the dev enviroment for testing new functions..

What would be the correct way to change between branches while using dev ? Is it correct to define the git tag ?

i use gitkraken, it msakes things very easy and visual which works best for me, i get confused using git from terminal, too much to remember when making so many changes so i have forgotten how to do it manually. but if youre wanting to dev, i would say install gitkraken and just add the folders in the dev for probe basic and qtpyvcp then you can preview all the latest and locked sown branches and have your own running branch.