You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The caller for }bedrock.cube.dimension.add has an optional parameter (pCtrlObj) which is either 1 or 0 to allow it to work on control objects. The clone cube is a clone of a control cube and is not being deleted even if pTemp is set to 1 because the pCtrlObj flag is not being inherited by the call to }bedrock.cube.delete later on in the process (it is set to zero instead of the value of pCtrlObj).
Suggest changing the 0 to inherit pCtrlObj.
Cheers.
To Reproduce
Steps to reproduce the behavior:
Create a control cube
Add a dimension to the control cube using }bedrock.cube.dimension.add ensuring pTemp is set to 1 (to delete clone cube) and pCtrolObj is set to 1 (to enable the cube to work on control objects).
Note that the clone objects have not been deleted. Process will have broken at that point.
Expected behavior
Clone objects deleted as per setting pTemp to 1.
The text was updated successfully, but these errors were encountered:
Describe the bug
The caller for }bedrock.cube.dimension.add has an optional parameter (pCtrlObj) which is either 1 or 0 to allow it to work on control objects. The clone cube is a clone of a control cube and is not being deleted even if pTemp is set to 1 because the pCtrlObj flag is not being inherited by the call to }bedrock.cube.delete later on in the process (it is set to zero instead of the value of pCtrlObj).
Suggest changing the 0 to inherit pCtrlObj.
Cheers.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Clone objects deleted as per setting pTemp to 1.
The text was updated successfully, but these errors were encountered: