Filter Editor doesn't remember what filter type is used after an "undo/redo" is done

[rickmastfan67]

Inkscape 0.48.4 r9939
Windows 7 x64

Steps to reproduce:
1. Draw anything (I recommend an Ellipse)
2. Filters > Shadows and Glows > Inner Shadow
3. Active the "Filter Editor" in the "Filters" menu. (Notice that the only filter there is the "Inner Shadow".)
4. Hit the Undo button.
5. Hit the Redo button.

What happens:
The redone filters name is "filter" in the "Filter Editor".

What should happen:
The name of the filter should be "Inner Shadow" like it was before the "Undo/Redo" in the "Filter Editor".

NOTE: This probably happens with all the other filters besides the "Inner Shadow", but since I saw this happening with it, that's how I'm reporting it.

[rickmastfan67 (rickmastfan67)]

Also, it seems that the "undo" breaks names for any other filters you want to add.

Substitute Step 5 above with this to see what I mean:
5. Filters > Shadows and Glows > Cutout Glow

What happens:
The new filter is called filter4643 (numbers part seems to be random).

What should happen:
The name of the new filter should be "Cutout Glow".

[jazzynico (jazzynico)]

Confirmed with Inkscape trunk revision 12011.
Fixed in revision 12012 with Bug #1089406 "filter name is random "filter232" when first added".

[su_v (suv-lp)]

Changes from r12012 reverted in r12137 due to unintended side effect with basic usage of the filter editor (see bug #1111459 for details).

[insaner (insaner)]

attached new patch in bug #1089406, please let me know if it fixes this issue too

[insaner (insaner)]

ok, revision 12232 should fix this.. if so, please assign to me and mark as fix committed.. thanks

[rickmastfan67 (rickmastfan67)]

~suv, can you do what insaner above requested please?

[rickmastfan67 (rickmastfan67)]

Is this bug fixed in 0.48.5 too with the backport of the bug #1089406 fix? If so, should the milestone for this be updated from 0.49 > 0.48.5?

[su_v (suv-lp)]

Fixed in stable release branch in revision 10000 with the backported fix for bug #1089406.