Inkscape 0.48+devel r10017
Xp sp3

There is a "Redo" entry under the Edit menu. But I'll never actually being able to use it.

I've considered posting ait as a bugreport, but I'm thinking that it's a planned feature for a future version of Inkscape.

Or is there any situations where Redo actually does work?


Thanks

Redo is not to repeat an action, but follows undo. For instance, draw an object. undo. your object has been undrawn. It's gone. Now redo. (It should tell you what you are about to redo, e.g. redo: draw path). Your object is back. select the object. Delete. Object gone. Undo. Object back. Redo. Object redeleted. If you never undo your redo will always be grayed out.

Thanks for clearing up.

Then I have misunderstood the concept about Redo.

Then I assume the Redo (do the same again) should be included as a function in Inkscape (wishlist).

Grobe wrote:Then I assume the Redo (do the same again) should be included as a function in Inkscape (wishlist).

Aren't you looking for a general 'Repeat last action' function (≠ Redo), like it already exists for extensions and filters - see menu 'Extensions > Previous Extension' (but not for regular commands)?

Related feature requests:

• Bug #171673 in Inkscape: “Repeating the last action”
• Bug #170131 in Inkscape: “Keyboard shortcut to repeat last operation”

~suv wrote:Aren't you looking for a general 'Repeat last action' function (≠ Redo), like it already exists for extensions and filters - see menu 'Extensions > Previous Extension' (but not for regular commands)?

Related feature requests:

• Bug #171673 in Inkscape: “Repeating the last action”
• Bug #170131 in Inkscape: “Keyboard shortcut to repeat last operation”

Sure, you're right. I just couldn't recall the name of that function as I wrote my post.

I've read those links you gave me. I must say WOW - it has been on the wish list for seven years now

I am curious as to how people picture a redo command in Inkscape. For some functions it seems obvious - the transformations*, for example, but for the drawing functions it seems ambiguous. If I am using the bezier tool and I add a node to a path, should redo add another node in the same location? The same distance away from the last node? What about the fill and stroke dialog? If I change the fill of an object, or add a stroke, what should redo do? Darken the fill? widen the stroke? How about the text tool? I enter some text on my page, then hit redo. Should it repeat the string of text in the same object? Create a new object on top of the old one? Just repeat the last letter?

It seems that the current setup - without redo - uses a large vocabulary of repeatable keybindings for actions that are unambiguously repeatable - and this system seems less confusing. A redo command might not require as much memorization of keyboard shortcuts, but that seems a slight advantage.
Not every concept from raster editing programs' interfaces translate into vector (or 3d, which I think has more in common with vector) interfaces.
I would definitely like to hear some ideas about implementation of this feature...

*a 'repeat transformation' menu command/keybinding would be nice, and I DO know that the dialog lets you keep 'applying', but when I drag/rotate/scale/skew an object on the canvas and then open the transform dialog, I expect (well, not any more ) to find the settings for my drag displayed in the appropriate boxes. What I find, though are the settings from the last time I used the dilaog - not as useful...

druban wrote:I am curious as to how people picture a redo command in Inkscape. For some functions it seems obvious - the transformations*, for example, but for the drawing functions it seems ambiguous. If I am using the bezier tool and I add a node to a path, should redo add another node in the same location? The same distance away from the last node?

It should do nothing. It should have no effect regarding adding new objects or manually alter a path.

druban wrote:What about the fill and stroke dialog? If I change the fill of an object, or add a stroke, what should redo do? Darken the fill? widen the stroke?

Nothing. Unless you select another object it shouldn't do anything.

druban wrote:How about the text tool? I enter some text on my page, then hit redo. Should it repeat the string of text in the same object? Create a new object on top of the old one? Just repeat the last letter?

Should not have any effect here, unless you alter just a part of the text. Then, if you select some other text, redo will make the new selection get the same format (size, color etc). Creating new objects and manually alter nodes wont have any effect on the tool.

druban wrote:It seems that the current setup - without redo - uses a large vocabulary of repeatable keybindings for actions that are unambiguously repeatable - and this system seems less confusing. A redo command might not require as much memorization of keyboard shortcuts, but that seems a slight advantage.

I partly disagree. I remember keybindings and prefer using keyboard over mouse for repetive tasks. However my opinion is that a "do again" function will make workflow more efficient.

druban wrote:Not every concept from raster editing programs' interfaces translate into vector (or 3d, which I think has more in common with vector) interfaces.
I would definitely like to hear some ideas about implementation of this feature...

You've got some thaugts from me now.

druban wrote:*a 'repeat transformation' menu command/keybinding would be nice, and I DO know that the dialog lets you keep 'applying', but when I drag/rotate/scale/skew an object on the canvas and then open the transform dialog, I expect (well, not any more ) to find the settings for my drag displayed in the appropriate boxes. What I find, though are the settings from the last time I used the dilaog - not as useful...

Agree. I think such a function would be useful mostly for transformations.

Here is a couple of practically examples:

I often use the same align button several times. A working redo function would really save a lot of time on that (rather than aiming the mouse at that little button)

Another one:
I have two objects. On object_1 I change one or more properties.
If I do a REDO on Object_2, then every properties that was CHANGED from Object_1 is copied to Object_2
Let say I for Object_1 change stroke width to 3 and fill opacity to 50. When select Object_2 and REDO, Object_2 also get stroke width=3 and fill opacity=50. No other properties should be affected.

Grobe wrote:Here is a couple of practically examples:

I often use the same align button several times. A working redo function would really save a lot of time on that (rather than aiming the mouse at that little button)

Another one:
I have two objects. On object_1 I change one or more properties.
If I do a REDO on Object_2, then every properties that was CHANGED from Object_1 is copied to Object_2
Let say I for Object_1 change stroke width to 3 and fill opacity to 50. When select Object_2 and REDO, Object_2 also get stroke width=3 and fill opacity=50. No other properties should be affected.

Hi Grobe. I know exactly what you mean about the align dialog. I think it would be nice to have keyboard shortcuts for the buttons in the align dialog - that way you would never even have to call up the dialog in the first place.

As for your second request I think the "paste style" command gives you something of this functionality right now. I DEFINITELY understand it's not exactly what you want.

I can still see lots of confusion for this 'redo' feature though.
What if the second object already has reduced opacity? should it be 50% of the current opacity?
What if I keep the first object selected and hit redo? I would expect the opacity to be reduced, but someone else might expect it to do nothing....
What if it's a group containing elements of varying opacity? Should the opacity be reduced for all to 50%? Should each object's relative opacity to the others stay the same??
Of course one can code in exception catchers for all these things but I'm just saying there's no way to know that what I expect to happen is what other people also expect to happen.
For instance in the example you gave above, I would expect the "redo" to ONLY do the fill opacity change because that's the last thing I did, I might be perturbed that it repeated the last TWO actions I performed (change stroke, change fill) but obviously you think of these as one action.
Likewise, if I scaled the width and height (in that order) of an object, then selected another object and did "redo", should the new object's width and height be scaled, or just its height? (On the other hand, using the transform dialog as it is now there would be no ambiguity...)
I'm not trying to start an argument here... these are just my ideas about your proposed feature...

HI.

Yes, I understand that ther must be an agreement on how this feature should work in practise.
One way to do this must be to add a new section for this under Properties, so that the user can change the behaviour of the redo function.
Otherwise, I'll guess (as I understand you) somebody will like it and some else would probably not take use of it.