| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |\ \ \ \ \ |
|
| | | | | | | | |
|
| | | |\ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | |\ \ \ \ \ \ |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | |_|/ / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | | |
Add fix to bspline when two cusp nodes arround a powered node
|
| | |\ \ \ \ \ \ \
| | |_|/ / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Work by Geoff Lankow (!72)
Also includes some fixes I found during review.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
While the spec explicitly allows for that (and it should disable
rendering of the element) Inkscape does not allow setting a zero
radius at runtime (it works fine when opening an existing file).
If we still force this during runtime we end up with a "ghost"
ellipse on canvas which looks as if it had the old radius but has
control points according to the zero radius and has the added bonus
of not being movable (or rather being movable but snapping back
back immediately when released) until updating the radius with a
valid number again which finally moves the ellipse to wherever it
should have been.
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
If an open arc is rendered we need to look at the prefixed values
instead.
|
| | | | | | | | | |
|
| | | | |/ / / /
| | |/| | | | |
|
| |\| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
It happen often that the rendering was interrupted early but the
final "cairo_surface_status" claims success which results in
incomplete output but no user-visible warning.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The previous implementation [1] allowed to sandwich text between
graphical objects by outputting multiple (partial) PDF pages which
are then stacked in the final document to reveal the full image.
However this code failed for clipped/masked/transparent objects
as those are treated specially by the renderer resulting in missing
pages in the output causing [2].
The attempt to workaround this issue which was committed in
e4dea66a338824037b6c35b262aa8db4004b6581 (now reverted)
fixed document creation in LaTeX by inserting blank pages but did
not actually fix the issue with clipped/masked/transparent objects
typically resulting in a single page with the full image and all
text put on top.
This commit resolves the underlying issue, making the former
workaround unnecessary and allowing for proper overlaying of text
and arbitrarily clipped/masked/transparent objects
Fixed bugs:
- https://bugs.launchpad.net/inkscape/+bug/771957 [1]
- https://bugs.launchpad.net/inkscape/+bug/1417470 [2]
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit e4dea66a338824037b6c35b262aa8db4004b6581.
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Now works unless configured with
ENABLE_BINRELOC or ENABLE_OSX_APP_LOCATIONS
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
These files are actually part of BinReloc
Inkscape specific code is in path-prefix.h (and now path-prefix.cpp)
|
| | |\ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Please confirm typos in the following
`doc/nr-filter-interface.txt`
`share/symbols/BalloonSymbols.svg`
.
|
| | |/ / / / / |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\| | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |\| | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | |/ / / / /
| |/| | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This ensures the (modal) dialog is positioned on top of the Inkscape
window in which the file will be opened.
Before it could happen that the dialog was not even on the same
monitor as the Inkscape window leaving Inkscape in a seemingly
inaccessible state if it was overlooked.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/1195929
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
see efb5cb4a7a22316994b7a89b51d3d0ca654dabd4
|