View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003664||Arch||Bug||public||2018-11-01 07:34||2019-09-13 09:31|
|Target Version||Fixed in Version|
|Summary||0003664: Visibility not preserved after making edits in building tree|
|Description||Using the BIM workbench, if you have several floors as building parts within a building. Hide the floors your not working on. Make an edit, such as moving an object, changing the width of a wall. The whole building becomes visible and have to go through hiding the levels not working on again.|
This seems to be a general thing, after any edit the visibilities are lost... making it quite frustrating if you need to make a few edits to a layer obscured by others. Another scenario where the same issue exists is where you need to hide a wall to get a good side profile of an internal wall. Same happens again... keep having to hide the outer wall on every edit.
|Steps To Reproduce|
|Additional Information||OS: Windows 7|
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15113 (Git)
Build type: Release
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedKingdom (en_GB)
bugreport_visibility.FCStd (20,913 bytes)
||Apologies If I've categorised this wrong, I'm new to this. Fairly sure this is a bug, rather than a feature...|
Found a workaround... it seems this only affects the visabilities with the same parent. So if I move the Ifc floor (building part) out from under the Ifc building. Hide the building and make edits to the floor in the root of the tree, the building object stays hidden. When the series of edits are finished I can move the building part back under the building.
This will remove some of the frustration, and allow faster work flow.
btw, thank you for your effort in putting this excellent program together. I am a developer, so when I've got some free time I might have a look over the source code and see if I can help.
Doing some tests here, the behaviour still happens if you use 2 groups instead of the 2 buildingParts, but not if the host is a group too instead of a Building.
If you place a third object directly inside the building, the bug happens with it too.
So the problem seems to be that the host building (which is actually also a building part) forces the visibility of its children on/off when you change a property of one of its children... This is weird. There is nothing related to visibility inside the BuildingPart code, but there might be a problem with the Gui::ViewProviderGroupExtensionPython...
This V0.19 issue seems related:
|2018-11-01 07:34||djmccorrie||New Issue|
|2018-11-01 07:34||djmccorrie||File Added: bugreport_visibility.FCStd|
|2018-11-01 07:36||djmccorrie||Note Added: 0012122|
|2018-11-01 07:41||djmccorrie||Tag Attached: BIM|
|2018-11-01 07:42||djmccorrie||Tag Attached: Visibility|
|2018-11-01 07:51||djmccorrie||Note Added: 0012123|
|2018-11-01 20:48||yorik||Note Added: 0012128|
|2018-11-01 20:48||yorik||Assigned To||=> yorik|
|2018-11-01 20:48||yorik||Status||new => assigned|
|2018-11-01 20:49||yorik||Note Edited: 0012128||View Revisions|
|2019-09-13 09:31||Roy_043||Note Added: 0013590|