Hi @jurgeng - as a workaround in case you need this fast, there are a couple extensions that rearrange pages (or playing cards). I haven't tried any of them, and can't make a recommendation, but perhaps you want to try them out. You will find them among these: https://inkscape.org/gallery/=extension/?q=page

This has already been implemented in 1.5-dev:

Seems like it might be an issue with the monitor hardware?

Since there isn't a stacktrace it's difficult to say yes (or no for that matter) to that question.

If you're able to install lldb (available through Xcode or possibly without it) and crash Inkscape while being run from lldb, we might be able to get a stacktrace.

Hi, thanks for the report!

Can you add a bit more info on what you were doing when the crash happened? The stacktrace indicates that it has something to do with LPEPerspectiveEnvelope and happened after the click of a button.

Can you also attach the problematic SVG file which caused the crash? Is the crash reproducible or does it happen intermittently?

Another thing to try would be to upgrade to 1.4.3 (https://inkscape.org/release/inkscape-1.4.3/) and see if that fixes the crash.

Hi, thanks for the report!

The trace is not rich enough to infer the cause. Are you able to collect a detailed backtrace?

Can you also record a screencast with the crash?

Hi, thanks for the report! This looks like inkscape#6028 (closed). Can you follow #13171 (comment 3035377816), that should fix it.

For some reason drawning.svg is never what I want to call my projects (I normally call my base files project.svg). This introduces a simple setting that allows the user to set the default name for new, unsaved projects.

Images

Default setting

Setting tweaked

Save Dialogue with tweaked setting

Notes

• This is my first contribution to Inkscape, apologies if this isn't a wanted feature or if the code seems out of convention.
• I love Inkscape, I use it a ton. Thank you to everyone who brings it to life!

Martin Owens (d4d38f3e) at 19 Mar 15:37

Agreed.

• Correctly render axonometric and modular grid when canvas is rotated
• Share the code for aligning to pixel grid
• Make the grid/guideline an ruler more consistent with each other
• Remove partial guideline gap on tile borders
• Make the rectangle grid x and y dashes better aligned (at least for pixel based grids and round zoom levels)
• Simplify and deduplicate parallel grid line calculations
• Some changes to grid configuration labels and tooltips

Fixes #1857

Detailed explanation

Main goal of the issue was fixing rotation. In the process I ended up simplifying refactoring a lot more of grid rendering than I expected. The old version had quite a bit of duplication with baked in assumptions about the view not being rotated.

The pixel snapping isn't perfect but it should behave a bit better and at least now it's in single place making it easier to do future adjustments while keeping the behavior of guides and multiple grid types the same.

In the current state it with perfect grid and zoom (px based grid, 100% or other round multiplier zoom) it should be more or less perfect and aligned with rulers. Can't get rulers and grid aligned for non px based (for example mm based) since the ruler has significantly different rendering logic doing things in blocks. With regards to rounding threshold, 0.5 is probably a bit too biased towards right, but the old approach of simply doing floor(x)+0.5 was worse and introduced inconsistency even for perfect grids. floor(x+0.0001)+0.5 might be mathematically more accurate while avoiding the problems of inconsistent rounding to floating point and other transformation producing numbers that close integer (9.9999 vs 10.00001), but the ruler seems to be even more biased towards right so for now kept floor(x+0.5) to keep them more similar.

I hope the label changes won't be too controversial. Made some of them in document properties match the ones from preferences and replaced the ones which where reused from rectangular grid with something more suitable for each type of grid. Also seems like the tooltips for rectangular grid were mixed up.

Comparison screenshots:

Click to download and inspect.

Other scenarios considered and at least partially tried during testing:

• flipping canvas horizontally/vertically
• rotating canvas 180 and how it affects dash alignment

Related issues:

Fixes #1857

Partially related to #794 although it's a bit of mess. Initial description complains about dots becoming crosses even though "before" screenshot also shows crosses just with lighter transparency and center looking darker from 2 overlapping semitransparent dashes and thus looking more like dot. Later discussion goes more in the direction of discussing misaligned rendering which this MR slightly improves. Wouldn't be surprised if there were some additional intentional changes between 0.92 and now.

• Correctly render axonometric and modular grid when canvas is rotated
• Share the code for aligning to pixel grid
• Make the grid/guideline an ruler more consistent with each other
• Remove partial guideline gap on tile borders
• Make the rectangle grid x and y dashes better aligned (at least for pixel based grids and round zoom levels)
• Simplify and deduplicate parallel grid line calculations
• Some changes to grid configuration labels and tooltips

Fixes #1857

Detailed explanation

Main goal of the issue was fixing rotation. In the process I ended up simplifying refactoring a lot more of grid rendering than I expected. The old version had quite a bit of duplication with baked in assumptions about the view not being rotated.

The pixel snapping isn't perfect but it should behave a bit better and at least now it's in single place making it easier to do future adjustments while keeping the behavior of guides and multiple grid types the same.

In the current state it with perfect grid and zoom (px based grid, 100% or other round multiplier zoom) it should be more or less perfect and aligned with rulers. Can't get rulers and grid aligned for non px based (for example mm based) since the ruler has significantly different rendering logic doing things in blocks. With regards to rounding threshold, 0.5 is probably a bit too biased towards right, but the old approach of simply doing floor(x)+0.5 was worse and introduced inconsistency even for perfect grids. floor(x+0.0001)+0.5 might be mathematically more accurate while avoiding the problems of inconsistent rounding to floating point and other transformation producing numbers that close integer (9.9999 vs 10.00001), but the ruler seems to be even more biased towards right so for now kept floor(x+0.5) to keep them more similar.

I hope the label changes won't be too controversial. Made some of them in document properties match the ones from preferences and replaced the ones which where reused from rectangular grid with something more suitable for each type of grid. Also seems like the tooltips for rectangular grid were mixed up.

Comparison screenshots:

Click to download and inspect.

Other scenarios considered and at least partially tried during testing:

• flipping canvas horizontally/vertically
• rotating canvas 180 and how it affects dash alignment

Related issues:

Fixes #1857

Partially related to #794 although it's a bit of mess. Initial description complains about dots becoming crosses even though "before" screenshot also shows crosses just with lighter transparency and center looking darker from 2 overlapping semitransparent dashes and thus looking more like dot. Later discussion goes more in the direction of discussing misaligned rendering which this MR slightly improves. Wouldn't be surprised if there were some additional intentional changes between 0.92 and now.

When adding printing marks to a multipage document, the printing marks appear on the adjacent pages (when just creating extra pages without manually moving them around).

I see two possible approaches:

1. Set wider (or customizable) gaps between pages
2. Adapt the size of the printing marks so they don't touch the next page

Hi, thanks for the report!

This is a duplicate of inkscape#5904 (closed) which was fixed in master. The fix seems simple enough to backport to 1.4.4.

The workaround for now would be to first select any page (most likely you'd want to select the last one) by clicking on it while using the Page Tool and then clicking on the button.

@doctormo the patch seems simple enough for a backportproposed, can this go into 1.4.4? (inbox#13337 (closed))

Hi I have an issue and, I looked for a most closely fitting open issue and this seems to be it.

I have create a handwritten svg that tries to load a font that is local and in the same directory. The svg works fine and is viewable in browsers and the ristretto image viewer.

When I try to open the file in inkscape with the context menu it just crashes silently and does nothing (bad), when I start inkscape via the GUI, I get a startup dialogue, if I select the svg there, it also crashes without error message.

If I launch inkscape via the terminal, I get this message in the terminal:

** (org.inkscape.Inkscape:12972): WARNING **: 11:12:44.672: end_font_face_cb: font face rule limited support.
  font-family : 'myfont';
  src : url(file:///path/to/my/font/MYFONT.ttf)

** (org.inkscape.Inkscape:12972): ERROR **: 11:12:44.672: end_font_face_cb: Failed to add: file:///path/to/my/font/MYFONT.ttf
fish: Job 1, 'inkscape' terminated by signal SIGTRAP (Trace or breakpoint trap)

Hope that helps. I am on xubuntu 24.04 . My version is Inkscape 1.2.2 (b0a84865, 2022-12-01) which is supposedly the newest version that is available via apt for me.