nds [Wed, 28 Jan 2015 06:30:04 +0000 (09:30 +0300)]
Issue #368 move constraint problem
The operation should be applyed if the apply state is true in the operation manager, otherwise, it is aborted.
The isOkEnabled, setOkEnabled methods should not be avaialabe in the property panel because this state is updated according to operation manager state by workshop object.
canAbortOperation is renamed to canStopOperation, because it is possible that the given operation is commited or aborted.
nds [Tue, 27 Jan 2015 14:22:08 +0000 (17:22 +0300)]
Issue #348 Validate sketch is disabled when point coordinates are set manually
The storeValue should happens only in the creation mode.
Erroneous case is the constraint lenght is moved by the edit start. The (0,0) point value is set to the feature by the operation start, point 2d control activation.
nds [Mon, 26 Jan 2015 08:22:48 +0000 (11:22 +0300)]
Issue #348 Validate sketch is disabled when point coordinates are set manually
It saves the clicked point, connects to the the activated signal of a widget and try initialize the widget with the point value.
There are some limitations:
Firstly, for the constraints distane we should not perform it because the fly out point is moved to the mouse, there is a blinking between calculated value and the clicked. It can be corrected if do not update the viewer during this. But, the lightes workaround is to do not apply clicked point to such type of operation.
Secondly, the mouse release point should be also saved in the clicked point for the mouse moving with Left button swithed. Without this, the actuvatedwidget value is moved to the previuosly clicked mouse but not the current one.
nds [Thu, 22 Jan 2015 09:02:50 +0000 (12:02 +0300)]
Issue #348 Validate sketch is disabled when point coordinates are set manually
Do not store value if the default value was not defined in the XML file.
It corrects setValue in the Point2D to update attributes even if the value are the same.
nds [Wed, 21 Jan 2015 09:33:50 +0000 (12:33 +0300)]
Regression correction: the axis is not displayed in the black dash-dots. The reason is displayer correction to do not perform redisplay if the presentation is not modified.
nds [Wed, 21 Jan 2015 06:39:05 +0000 (09:39 +0300)]
Issue #351 constraint is not applied on preselected segments
The reason: lost selection of the circle center.
The decision: do not perform redisplay the AIS presentation in the AIS_InteractiveContext(displayer) if the shapes are equal. Here the GeomAPI realisation is necessary. The TopoDS_Shape realisation of the isEqual method is not enough because different TShapes instances are created and isEqual returns false.
A correction in the widget shape selector to avoid the distance presentation update by set an object(before set an attribute). In the previous version, the distance was jumped by selecting two points on lines. The reason is the distance calculation between point-object by setObject and after that point-point by setAttr
nds [Tue, 20 Jan 2015 14:54:42 +0000 (17:54 +0300)]
Issue #351 constraint is not applied on preselected segments
The reason: lost selection of the circle center.
The decision: do not perform redisplay the AIS presentation in the AIS_InteractiveContext(displayer) if the shapes are equal. Here the GeomAPI realisation is necessary. The TopoDS_Shape realisation of the isEqual method is not enough because different TShapes instances are created and isEqual returns false.
A correction in the widget shape selector to avoid the distance presentation update by set an object(before set an attribute). In the previous version, the distance was jumped by selecting two points on lines. The reason is the distance calculation between point-object by setObject and after that point-point by setAttr
