nds [Mon, 9 Nov 2015 08:46:13 +0000 (11:46 +0300)]
#816 In multi-rotation, be able to put the total angle or the step angle (Rotation only)
Realization for Translation
WidgetPoint2d is corrected because multi translation can have equal points -> single end point value = full end point value when number of objects = 2.
nds [Mon, 9 Nov 2015 05:16:32 +0000 (08:16 +0300)]
#816 In multi-rotation, be able to put the total angle or the step angle (Rotation only)
It must also be possible to enter the full angle value of the multi-rotation, with a toggle button defining the semantic of the angle value (either full rotation or between two consecutive repetitions).
For consistency, it should be the same for multi-translation.
nds [Fri, 6 Nov 2015 16:14:03 +0000 (19:14 +0300)]
#816 In multi-rotation, be able to put the total angle or the step angle (Rotation only)
It must also be possible to enter the full angle value of the multi-rotation, with a toggle button defining the semantic of the angle value (either full rotation or between two consecutive repetitions).
For consistency, it should be the same for multi-translation.
nds [Fri, 6 Nov 2015 15:49:02 +0000 (18:49 +0300)]
#816 In multi-rotation, be able to put the total angle or the step angle (Rotation only)
It must also be possible to enter the full angle value of the multi-rotation, with a toggle button defining the semantic of the angle value (either full rotation or between two consecutive repetitions).
For consistency, it should be the same for multi-translation.
nds [Fri, 6 Nov 2015 08:42:03 +0000 (11:42 +0300)]
Issue #995: Checkbox 'Make a copy' during translation and rotation operations
Correction from a list of improvements:
For compatibility with old GEOM, we must ask for the total number of objects, not the number of copies, as currently (for information, it's like that too in SolidWorks).
nds [Fri, 30 Oct 2015 16:02:37 +0000 (19:02 +0300)]
Simplification of the code: it removes focusNextPrevChild processing.
It is not enough to emit signal about focus change here because it can be changed by mouse click in another control. It is not processed in this method.
The same functionality(to store modified value on focus lost) is realized in ::deactivate() of the model widget and processEnter method of the widge.
nds [Fri, 30 Oct 2015 07:31:18 +0000 (10:31 +0300)]
Activating of another widget by hands should be performed only after store the current widget value ot the model only when the operation sate is Modified in Property Panel.
nds [Wed, 21 Oct 2015 15:18:09 +0000 (18:18 +0300)]
A correction for the parameters:
after entering the parameter name, when the value input gets the focus,
an error message is displayed (unnexpected EOF while parsing (<string>,
line 0) while the user didn't type yet anything. It's not fair.
The decision: do not set the editor value to the feature attribute by the control activation.
nds [Thu, 15 Oct 2015 15:35:44 +0000 (18:35 +0300)]
Value state is provided in ModelWidget to remove 'myIsCurrentValueUnderModification' in sketch manager. Reason: Apply button should be disabled during value modification for any operation, not only Sketch.
nds [Wed, 14 Oct 2015 11:01:24 +0000 (14:01 +0300)]
The flyout widget should not accept the focus if the corresponded presentation is not built on the feature attributes.
Case: create a contour, select any vertex, detach it from a line. Call distance and select the equal points of detached lines. Previous result: no active control, waiting for user click. Current result: the flyout attribute is initialized with a default value, the focus is on the value control.
