Enable/disable snapping not properly recorded in edit history

Bug #1064858 reported by Formerly Kevin Yin, now disabled on 2012-10-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
High
Unassigned

Bug Description

Inkscape 0.48 on Windows 7 64-bit

To reproduce:
Open the edit history panel.
Enable snapping.
Press Ctrl+Y to redo.

What happens:
When you enable snapping, a blank entry appears in the edit history, but inkscape doesn't jump to the blank entry as it normally does, and the blank entry doesn't appear until you try to redo. Trying to click on other entries in the edit history sometimes causes jumps to the blank entry, and sometimes Redo causes the edit history panel to jump around wildly.
There is probable memory corruption.

Specifically, Inkscape 0.48.2 r9819

Inkscape crashes if you fiddle with a bugged edit history too much.

su_v (suv-lp) on 2012-10-10
tags: added: snapping undo
su_v (suv-lp) wrote :

> To reproduce:
> Open the edit history panel.
> Enable snapping.
> Press Ctrl+Y to redo.
>
> When you enable snapping, a blank entry appears in the edit history, (…)

Not reproduced with Inkscape 0.47, 0.48.0, 0.48.2 and 0.48.3: there is no empty entry added in the 'Undo' history when toggling snapping on / off (either via button on the snap controls bar, or via menu 'View > Snap'). Message in the status bar is 'Nothing to redo.'

Could you please
1) provide details about your version of Inkscape (see Inkscape menu 'Help > About Inkscape').
2) provide more details about the circumstances of how to reproduce the reported issue (based on default preferences and a new document based on the default template).

Changed in inkscape:
status: New → Incomplete
su_v (suv-lp) wrote :

> Not reproduced with Inkscape 0.47, 0.48.0, 0.48.2 and 0.48.3
Tested on Mac OS X 10.5.8 and OS X 10.7.4.

su_v (suv-lp) wrote :

> Not reproduced with Inkscape 0.47, 0.48.0, 0.48.2 and 0.48.3

Nevermind - reproducible when using either the keyboard shortcut to toggle snapping, or the menu entry (my mistake for sloppy testing), but not with the button on the snap controls bar.

Also present in current trunk (r11774):

** (inkscape:53942): WARNING **: Incomplete undo transaction:

** (inkscape:53942): WARNING **: Event: Set attribute inkscape:snap-global to "false" on #<Element:0x0x1116d3580>

Changed in inkscape:
importance: Undecided → High
status: Incomplete → Confirmed
su_v (suv-lp) wrote :

Also present in Inkscape 0.46.

su_v (suv-lp) wrote :

Attaching backtrace (using --g-fatal-warnings) with debug build of current trunk on OS X 10.7.4

Steps (default preferences, default template):
1) launch inkscape
2) toggle snapping off with keyboard shortcut '%'
3) redo

su_v (suv-lp) on 2012-10-10
Changed in inkscape:
status: Confirmed → Triaged

I haven't been able to reproduce this bug; I guess it's been solved?

Closing the bug now, but if I'm mistaken then just let me know!

Changed in inkscape:
status: Triaged → Fix Released

Bug still exists, using the process in comment 8.
0.91pre3 64 bit, Windows 8.

Changed in inkscape:
status: Fix Released → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers