Jump to navigation Jump to search
- 1 Inkscape 0.45: overview
- 2 Undo history
- 3 Speed
- 4 Command line
- 5 Misc improvements
- 6 Bugfixes
- 7 Tools
- 8 Translations
- 9 Known problems
Inkscape 0.45: overview
- Inkscape now features a History Dialog accessible through [CTRL] + [SHIFT] + H or Edit→Undo History. All changes to the document since it was opened are recorded here.
- In the dialog, changes are listed from the oldest (top) to the newest (bottom).
- The type of each change is indicated by an icon and a short description.
- For readability, consecutive changes of the same type are placed in a collapsable branch showing a triangle marker and the number of the hidden actions in the branch.
- By clicking on an event event in the list, you can easily move through the undo history, i.e. undo or redo any number of actions with one click.
- The Undo and Redo commands in the Edit menu display the descriptions of the commands to be undone and redone, correspondingly.
- Interruptible display: Previously, Inkscape could not do anything until it finishes the current screen redraw. Now the redraw is made interruptible, so that Inkscape responds to mouse and keyboard input and can abort the current redraw and start over if you do some screen-changing operation. As a result, Inkscape now feels much snappier and more interactive.
- Radial gradients are rendered faster by at least 10%.
- Screen render is faster by 2-3%, up to 5% for complex drawings with transparency.
- Display is more responsive when working at high zoom levels when using a tablet.
- Rendering (compositing) quality has been improved. This is most visible with (partially) transparent gradients, banding is a lot less pronounced now. Speed has also been improved in some cases.
- The new
--export-pdfcommand line parameter allows exporting an SVG image to PDF from command line.
- [new cursors - scislac]
- Exported PNG images have the correct resolution set in the headers.
- A new Cairo-based PDF exporter has been added to Inkscape. Inkscape 0.45 can export shapes, strokes, transparency, gradients, patterns, text, and images correctly to Cairo. While clipping paths and masks are known to be faulty or missing. Cairo will write a PDF with vector graphics when possible and fall back to raster graphics when needed. What can be exported as vectors and how much of the image will be rasterized when the fallback kicks in depends on your version of Cairo. Cairo version 1.2 with the pdf backend compiled in is the minimum requirement for any Cairo-based PDF exports.
- The native PDF exporter introduced in Inkscape 0.44 is improved along with the new Cairo-based PDF exporter. Changes since Inkscape 0.44 include: New features: bitmap images can be embedded, pdf files can be exported from commandline. Changed behaviour: the pointless text to path question is gone. Fixed bugs: save failure is now detected, miter limits are now >= 1, pdfs with transparent gradient are now embeddable, eccentric elliptic gradients fixed, dash style inheritance fixed, transparency inheritance fixed.
- [expand/contract selection in node tool, sculpt profiles - bbyak]
- Simplify Path now had two modes when working with a group of paths: the default mode, which treats all of the paths as one large object to simplify, or the new mode, which acts the same as using Simplify on each path in a group separately. In preferences.xml, set options.simplifyindividualpaths to 1 to get the new mode.
- For long Simplify operations (more than 20 paths at a time), Inkscape provides user feedback via the status bar as to how many paths have been simplified. This change also prevents Inkscape from appearing to have locked up during the operation.
- When deleting a node, update neighboring smooth nodes to be cusp nodes because symmetry is broken.
- Instead of the confusing toggle button, now the Controls bar for the Dropper tool has two checkboxes, "Pick alpha" and "Set alpha", which work as follows. Suppose you have an object selected and, using Dropper, click on an object which has red (#FF0000) fill and 0.5 opacity (half-transparent).
- If the "Pick alpha" checkbox is off, the selected object will get the fill color #800000 (i.e. faded-out red) and fill opacity will be at 1.0 (opaque).
- If the "Pick alpha" checkbox is on but "Set alpha" is off, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 1.0.
- If both "Pick alpha" and "Set alpha" are on, the selected object will get the fill color #FF0000 (red) and fill opacity will be at 0.5 (half-transparent).
- If you Shift+click instead of click, the same changes will be made to stroke color and stroke opacity, correspondingly. Note that in no situation can Dropper change the master opacity of the selected object(s), although it can pick it just as it does any other kind of opacity.
- Remarkable improvements are the Danish, Finnish, Nepalese and the Vietnamese translation of the user interface. They all jumped from 0 to 100 percent in a very short timespan.
Problems with some Debian libgc-6.7 packages
- Inkscape will hang or crash when linked with the first Debian packaged version of the Boehm garbage collection library. This problem was fixed in version 1:6.7-2 of the package. If you have libgc 6.7 on your Debian-based system, make sure that you are using that version of the package or later.
Beware of defective themes on Linux
- Inkscape and other Gtk programs can crash on any Linux, when the gtk2-engines-smooth / libsmooth package is installed. We have filed a bug against libsmooth which is now in gtk-engine and part of gnome. Removing the package resolves the problem. Update: this bug appears to be fixed in newer versions of gtk-engines. If you are affected by this problem please update to a newer version of gtk-engines. If problems persist then please inform the gtk-engines maintainers of the problem.
- A similar crash happens if the KDE Baghira theme or the package gtk_qt_engine are installed. If you experience Inkscape crashes on KDE, please try to install a different theme from Baghira, or uninstall the gtk_qt_engine package from your system. Both problems also affect older versions of Inkscape.
- If you were using certain CVS/SVN builds from autumn of 2005, you may have the file
menus.xmlhanging around in your profile directory (e.g.
~/.inkscapeon Linux). In that case you will see many errors about verbs that cannot be found, and some commands in menus will be disabled. Make sure to delete
menus.xmlto fix this.