| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
still needs to be updated)
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
js/document/models/html.js
js/document/views/design.js
Signed-off-by: Valerio Virgillito <valerio@motorola.com>
|
| |
| |
| |
| | |
selection change handler
|
| |
| |
| |
| | |
handles (the behavior now matches the design)
|
| |
| |
| |
| | |
renders properly if we go through debugger)...also removed calls to getStageElement from pen tool
|
| | |
|
| | |
|
| |
| |
| |
| | |
Pen minus subtool not removing 1 anchor paths
|
| |
| |
| |
| |
| |
| | |
(can now select the pen plus, pen minus subtools) AND
add keyboard shortcut for brush tool
|
| |\ |
|
| | |
| | |
| | |
| | | |
PEN-MINUS subtool)
|
| | | |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
deleted)....this is buggy when the second anchor of a two-anchor subpath is deleted (since the first anchor needs to be converted back into stage world coords)
|
| | | |
| | | |
| | | |
| | | | |
essentially forces the need for a keyboard...must be addressed by a fix later on)
|
| | | |
| | | |
| | | |
| | | | |
---behavior is unchanged, but the realtime feedback for the tool (i.e. mouse cursor) will correctly reflect that a click after closing a path will start a new path, not add to that path
|
| | | |
| | | |
| | | |
| | | | |
1532 Pen: Anchor points get carried over to the new document
|
| | | |
| | | |
| | | |
| | | | |
(check if the second mouse click actually selects the existing first anchor point)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The elementModel is now a getter that will create a new model when needed.
Signed-off-by: Valerio Virgillito <valerio@motorola.com>
|
| |_|/
|/| |
| | |
| | | |
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
WorkingBranch
Conflicts:
js/components/layout/tools-list.reel/tools-list.html
js/components/layout/tools-properties.reel/tools-properties.html
js/components/tools-properties/brush-properties.reel/brush-properties.html
js/components/tools-properties/fill-properties.reel/fill-properties.html
js/components/tools-properties/pen-properties.reel/pen-properties.html
js/components/tools-properties/pencil-properties.reel/pencil-properties.html
js/components/tools-properties/selection-properties.reel/selection-properties.html
js/components/tools-properties/shape-properties.reel/shape-properties.html
js/components/tools-properties/tag-properties.reel/tag-properties.html
js/components/tools-properties/text-properties.reel/text-properties.html
|
| |/
| |
| |
| |
| |
| | |
creation
Signed-off-by: Valerio Virgillito <valerio@motorola.com>
|
|/
|
|
| |
have chips in the sub tool bar. Still need to complete adding chips to the Brush tool and finalizing the subtool bar layout to our spec for all of the subtools.
|
|
|
|
| |
file open
|
| |
|
|
|
|
| |
to shift in center of rotation
|
|
|
|
| |
(was a bug with starting drawing in those planes)
|
|
|
|
| |
coordinates), use stage world mouse positions to translate the anchor points while dragging
|
|
|
|
| |
tracking it by the pen tool. This fixes the bug where the canvas transform was incorrectly applied when the stroke width was changed
|
|
|
|
| |
decide to, later)
|
| |
|
|
|
|
| |
editing in 3D
|
|
|
|
| |
preserves the correct transformation applied to the subpath. This is a good snapshot of the polyline drawing in 3D (with some minor bugs).
|
|
|
|
| |
still have bug with shift when the bbox of the path grows (due to missing translation)
|
|
|
|
|
|
| |
YZ, XZ planes.
Current bugs: if the new point increases the bbox of the canvas, the entire canvas is shifted (due to inconsistency with center of rotation) AND the first two points added to planes other than XY have incorrect local coordinates (due to missing local coordinates)
|
|
|
|
| |
from local to global coords (the latter should be a temporary change as I will significantly change this)
|
|\
| |
| |
| |
| | |
Conflicts:
js/tools/PenTool.js
|
| |
| |
| |
| |
| |
| | |
of whether they are 2d shapes or WebGL shapes.
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| |
| |
| |
| |
| |
| | |
cache because they can easily get out of sync with the actual colors and materials. Instead, we will always query the object for these values.
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
js/document/templates/montage-html/default_html.css
js/mediators/element-mediator.js
js/panels/properties.reel/properties.js
js/tools/BrushTool.js
js/tools/LineTool.js
js/tools/PenTool.js
js/tools/SelectionTool.js
js/tools/ShapeTool.js
js/tools/TranslateObject3DTool.js
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | |
| | |
| | |
| | | |
prev, next) handles and hit testing in 3D. Update of the canvas with a transformation on it will modify the canvas incorrectly, and will be completed after merging with master
|
| | |
| | |
| | |
| | | |
world) point when there is no canvas yet
|
| | |
| | |
| | |
| | | |
tool the canvas size over the specified limit
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
canvas position
AND
some code cleanup (remove canvas left and top tracking for each subpath)
AND
add flags for the specifying in what coordinate space we're sampling the subpath
|
| | |
| | |
| | |
| | | |
correctly (except for incorrect canvas translation). Using cleaned up and re-factored version of the code. Not suitable for testing.
|
| | |
| | |
| | |
| | | |
canvas exists....AND...good state for code that works in 3D as long as the path was originally created in XY plane of the stage
|