To elaborate, there are two programs for defining zones for the local user. The first is the Map Registration application, which takes a SLAM map and transforms the coordinates between it and a regular floorplan. This will be my first time working with QtDesigner instead of hard-coding the visual elements, but I also think this will be better to manage as the number of tools increases. Now that we are working with a UI that is going to have multiple tools, I need the options and data for those tools to only be visible each time a tool is selected. I’m not entirely sure how to tackle this approach yet, and will require some design thoughts. I like the thought of a tabbed interface, but I’m not sure how to do that. Penn and I talked about having a drop down menu that sends a signal when it changes. Depending on the current selection, it would hide or show other widgets. Right now we are using OpenCV’s affine transformation tool to calculate the difference in points between the two maps. I was thinking about how to handle the exported map, but there are some incompatibilities between openCV and PyQt that might take too long to properly address.
This week, I also learned a decent amount about the different coordinate systems in Qt. For example, I implemented zooming by use of the scroll wheel, but zooming in does not affect any of the coordinates since I am zooming the entire QGraphicsView but the coordinates are taken from the pixels on the maps themselves. I currently have a small bug that leaves remnants when zoomed in, but I think that this might be a problem with the bounding rectangles of the child objects in the scene.

Below is our current implementation for Map Registration (excluding zoom)