-
-
Notifications
You must be signed in to change notification settings - Fork 5k
CAM: Refactor stock used as boundary to be distinct from regular stock #25960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This commit makes boundary stock objects distinct from regular stock by setting a boundary flag and label, and prevents editing of boundary objects in the job view provider. src/Mod/CAM/Path/Dressup/Boundary.py: - Add promoteStockToBoundary method, set boundary properties, handle missing stock/shape src/Mod/CAM/Path/Main/Gui/Job.py: - Block editing for objects flagged as boundary stock
|
I don't understand this. |
I had shown you this in a call a few days back. The boundary dressup make use of stock to specify a region to include / exclude for operations. If you click on THAT stock item in a attempt to modify it (like you can normal stock) it opens up the Job, and you end up modify the job's stock instead of the dressup's stock. This PR changes the name from Stock to Boundary, and the IsBoundary property. |
|
Now it clear |
StockvsBoundary-2025-12-06_12.58.39.MP4 |


This commit makes boundary stock objects distinct from regular stock by setting a boundary flag and label, and prevents editing of boundary objects in the job view provider.
src/Mod/CAM/Path/Dressup/Boundary.py:
src/Mod/CAM/Path/Main/Gui/Job.py:
Before/After

New property (Normally Hidden)
