| Commit message (Collapse) | Author | Age |
... | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
maximum value.
IKNinja-1236 - Corner radius is not applied if stroke size is >= 2 times the corner radius.
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
background-image gradient support.
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | |\ \ \ \ \
| | | | |_|/ /
| | | |/| | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| |\ \ \ \ \ \ |
|
| |\ \ \ \ \ \ \
| | | |_|_|/ / /
| | |/| | | | | |
|
| | |\ \ \ \ \ \
| | | |_|_|/ / /
| | |/| | | | | |
Allow users to toggle application of stroke and border settings when using the ink bottle tool. Also, fixed translate tool's handles to draw without stage's zoom.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | | |\ \ \ \ \
| | | | | |_|/ /
| | | | |/| | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
the ink bottle tool.
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| | | | |_|_|/
| | | |/| | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
in zoom code.
Signed-off-by: Nivesh Rajbhandari <mqg734@motorola.com>
|
| |_|_|_|/ /
|/| | | | |
| | | | | |
| | | | | | |
event handlers. Bind Timeline to currentSelectedElement. Various bug fixes.
|
|\| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Kruti Shah <kruti.shah@motorola.com>
|
| | | | | | |
|
|/ / / / / |
|
|\| | | | |
|
| |\ \ \ \
| | | |/ /
| | |/| | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
file open
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
js/helper-classes/3D/view-utils.js
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | |