| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
group's opacity)
|
| |
|
|
|
|
|
|
|
|
| |
- use hexadecimal color code as a replacement in this case.
- do not attempt to translate empty string / color name
- fix an issue in the custom trim() function returning early for
strings only consisting of a single whitespace character, e.g. "\n"
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/1743708
|
| | |
|
| |
|
|
|
|
| |
- fold _addResponseButton into addResponseButton
- remove unused setDefaultResponse
- includes cleanup
|
| |
|
|
|
|
|
| |
panel.cpp contains a lot of code which is actually used to build the
SwatchesPanel. Move it to swatches.cpp.
This is mostly just a cut-n-paste, plus some includes cleanup.
|
| | |
|
| | |
|
| |
|
|
| |
All the dialogs have a top-right "close" button, so this is now useless.
|
| |
|
|
|
| |
It was used only by the Memory dialog, which can very well add the
"Recalculate" button itself.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Replace "\stackrel" with "\tabular" to achieve constant line spacing.
The former varies line spacing depending on the content of the line
(i.e. an line containing "-" will have a very small height)
Add basic support for line-height.
(currently only the top level text element is considered)
|
| |
|
|
|
|
|
| |
Fixed bugs:
- https://bugs.launchpad.net/inkscape/+bug/448728
- https://bugs.launchpad.net/inkscape/+bug/1360213
- https://bugs.launchpad.net/inkscape/+bug/1654469
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This was broke in 2abe0bb681044d972e171189395a2afdbc39bf28 when delta_y
was applied in the opposite Y direction but baseline_shift was kept
unchanged.
|
| |\ \ |
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | |/ /
| |/| | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Separate new gradient on fill or stroke preference for meshes from linear/radial gradients.
This fixes a bug where changing the choice for the gradient tool is not reflected in the
mesh toolbar properly (and visa-versa).
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Fix broken window size/position restoration after gtk3 deprecation
fixes in fa8a2ee7e2539b145a87ac9af0d9748effa91631
- Use monitor geometry of the monitor Inkscape will be shown on
instead of defaulting to the primary monitor which is often wrong
- Let gtk+ / window manager handle window size/position sanitization
(confirmed working on Windows and Ubuntu 16.04) and remove custom
code which was prone to errors and did not always work as desired
- Make default window size "Small" work again (was broken in gtk3)
and add a new preference "Default" which uses the native window
size (i.e. tries to make just enough room for all controls)
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Clamp "Small" window size to 600x600
Everything smaller seems pretty unusable but can be discussed.
This fixes bug #1659256.
- Make sure "Large" window size is at least as large as "Small"
to avoid embarassing user reports.
- add "Default" as new window size and (surprise) make it the default
This will not influence the initial size request at all and
should result in the natural window size (unless overriden by the
window manager) and should be a suitable default for all cases.
Fixed bug:
- https://bugs.launchpad.net/inkscape/+bug/1659256
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- when restoring from document:
use monitor closest to stored document location on screen
- when using default size:
use monitor Inkscape is launched on (we always used this before)
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Exploit that an unmapped window's size/position is automatically
adjusted when it is first mapped which can be emulated by moving the
window while it is hidden.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Inkscape does not necessarily start on the primary monitor.
GTK+ did not reveal it's secrets (i.e. it seems undocumented) but
empirically the monitor having the cursor is the monitor the initial
window will be placed on.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
GTK+ / window managers handle positioning of new windows on the
screen just fine, so don't do "our own thing" that is prone to errors.
Notably the previous code for gtkmm >=3.22 was broken as it assumed
Inkscape to be shown on the primary monitor and mixed coordinates
relative to the primary display with absolute screen coordinates
|
| | | | |
| | | |
| | | |
| | | | |
(failed on Windows)
|
| | | | | |
|
| | | | |
| | | |
| | | | |
Found via `codespell`
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | | |
bool widget labels
|
| |/ / /
| | |
| | |
| | | |
Also fix a double XML write in path parameter unnecesary
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
results found')
|