FreeCADView Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004071 | Path | Feature | public | 2019-07-26 17:54 | 2021-02-06 06:33 |
| Reporter | dhka2 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | confirmed | Resolution | open | ||
| Target Version | 0.20 | ||||
| Summary | 0004071: Job path visualization | ||||
| Description | Currently the Job object contains a visualization of the gcode of all child "Operations" objects and all Operations. This visualization is identical to the one shown when all "Operations" objects are visible, and also identical to the visualization that is shown when all operations (ie children of the operations object such as a drill object) are visible. I propose that the Job object should not contain a visualization of the child object paths as this is redundant. Additionally making the Job object invisible should make all child objects invisible, without chaingeing their visibility state, so that making the job visible again shows all objects that where visible before the hiding of the Job object and only these objects. I also propose that the "Operations" Object behaves in the same manner with regards to the its children (ie the operations as a drill object). | ||||
| Additional Information | Note: this ticket has a Bounty (link) | ||||
| Tags | Bountysource | ||||
| FreeCAD Information | |||||
|
|
Forum thread |
|
|
How should toggling visibility of the job affect visibility of non-path child objects (stock, model, tool controllers, etc)? |
|
|
In exactly the same manner as path objects. the general point here is that the user, after generating a path with the path wb, needs only to hide the job object (or objects for a multi-body fcstd file) if he wishes to go back to the part workbench to make further modifications to the model. Then when the modifications are complete the user only needs to unhide the job object to continue work in the path wb. |
|
|
I have not looked at the code, but as a user it is my opinion, that if technically feasible, this should not be specially implemented in the path wb. As a general rule, for consistency and to avoid code duplication the behaviour should be as follows freecad wide: All objects are hidden except objects that have: A. Their visibility flag set to true AND B. The visibility flags of all parents up to document root (Application) are set to true. Also, as a general rule, objects that are expected to have children (ie are containers) should not have any visible elements at all unless there is a good reason to do otherwise, such as in the case of patterns or path dressups |
|
|
https://www.bountysource.com/issues/77869088-job-path-visualization |
|
|
This ticket has been migrated to GitHub as issue 5970. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-07-26 17:54 | dhka2 | New Issue | |
| 2019-07-26 17:55 | dhka2 | Note Added: 0013385 | |
| 2019-07-26 18:54 | sliptonic | Note Added: 0013386 | |
| 2019-07-26 19:31 | dhka2 | Note Added: 0013387 | |
| 2019-07-26 19:36 | dhka2 | Note Edited: 0013387 | |
| 2019-07-26 19:56 | dhka2 | Note Added: 0013388 | |
| 2019-07-26 20:03 | dhka2 | Note Edited: 0013388 | |
| 2019-07-26 20:03 | dhka2 | Note Edited: 0013388 | |
| 2019-07-28 15:53 | sliptonic | Note Added: 0013390 | |
| 2019-07-30 12:42 | Kunda1 | Tag Attached: Bountysource | |
| 2019-07-30 12:43 | Kunda1 | Description Updated | |
| 2019-07-30 12:43 | Kunda1 | Description Updated | |
| 2019-07-30 12:45 | Kunda1 | Status | new => confirmed |
| 2019-07-30 16:12 | Kunda1 | Description Updated | |
| 2019-07-30 16:12 | Kunda1 | Additional Information Updated | |
| 2021-02-06 06:33 | abdullah | Target Version | => 0.20 |
