| Commit message (Collapse) | Author | Age |
|\ |
|
| |
| |
| |
| |
| |
| | |
creation
Signed-off-by: Valerio Virgillito <valerio@motorola.com>
|
| |
| |
| |
| | |
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)
|
|
|
|
| |
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
|
| | |
| | |
| | |
| | | |
than XY
|
| | | |
|
| | |
| | |
| | |
| | | |
left and top change causes the rest of the points to move, which *may* be unavoidable), still has bugs with NEW points being placed at wrong position
|
| | |
| | |
| | |
| | | |
with canvas and/or stage transformation). Dragging does not yet work in case of canvas transformation
|
| | |
| | |
| | |
| | | |
handles separately, AND more hit testing with local coordinates
|
| | |
| | |
| | |
| | | |
canvas, and with a rotated view
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
display for new paths
|
| | |
| | |
| | |
| | | |
and path overlay (code needs cleanup)...still buggy if creating new paths
|
|\ \ \
| | |/
| |/|
| | |
| | | |
Conflicts:
js/tools/PenTool.js
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Reworked the add and remove elements into 1 function which can take 1 or more elements.
Removed the _element from the selection array
Many other changes related to those 2 changes
Undo/Redo shortcuts are now using montage undo/redo manager.
Signed-off-by: Valerio Virgillito <valerio@motorola.com>
|
| | |
| | |
| | |
| | | |
transformation applied to the element canvas and the stage canvas. Still quite buggy.
|
| | |
| | |
| | |
| | | |
(correctly setting the canvas for brush stroke file I/O, correct plane matrix for file I/O)
|
| | |
| | |
| | |
| | | |
out when to translate the subpath per canvas translation...this one seems to not drift (no floating point issues uncovered so far)
|
| | |
| | |
| | |
| | | |
roundoff errors when constantly changing stroke width
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to position the canvas on which the path is rendered
AND
add data-montage- to the ids in the pen and brush reels
AND
fix a bug with pen stroke transparency not working
|
| | |
| | |
| | |
| | | |
everything selected gets deleted (even if we have a selected subpath)
|
| | |
| | |
| | |
| | | |
cursors correctly over the exact mouse position AND reduce the radius (distance threshold) for picking paths
|