Select last but


What command to select last but one selection ?

I keep coming across this need.



(John Brock) #2

Sorry, I need a more complete description.
There is a SelLast command and I assume you already found that.

There are a ton of selection commands.
To get the list, type “Sel” and browse through the auto-complete list.

If you don’t find what you need there, please reply back with a better description.


I think he wants SelNextToLast… unfortunately it does not exist… --Mitch

(John Brock) #4

I guess I’d need to understand the work-flow to understand the need.

So draw a circle, then draw a line. Run this hypothetical “SelPenultimate” tool and the circle would be selected?

(Pascal Golay) #5

Probably a list of the last X number created objects is possible, analogous to UndoMultiple- you pick from the list.



That’s eminently scriptable with FirstObject()/NextObject(), but is it the last created objects he wants or the last selection set?



undoselecet would be nice

(Margaret Becker) #8

? UndoSelected is already a command.


I mean undo affecting the selection set, not the selected objects.

If memory serves me TSplines puts the selection movements on the undo stack.

edit: I checked, TSplines adds selection sets, not selecting undo. Photoshop has selecting in the undo stack.



I need to select last but one, not the last object selected but the one selected before that .
dont know how else to say it,

I shall explain further…this is just one example

  1. select an object and copy in place
  2. ctrl F …my keybd shortcut to select last created object, as I have discovered its not the one in yellow !
  3. move it somewhere and allocate it to a different layer
  4. now to find amongst the many that were all in line one behind the other the one I had selected before making that copy.


( #11

If History is enabled - Select Parent will work


The command that you want is called SelPrev

The problem is SelPrev tends to be buggy and not very effective.
If you copy and object and then immediately run selprev , it will select the original.
If you then run sellast the selection will switch to the copy.
However if you run sellast before you run selprev then selprev will no longer select the original object that was copied.
This looks like a bug to me. If it is designed behavior - its stupid and counter-productive.


thats what I need but I would be running sellast before selPrev so if its bugged its not of use.

Guess this is a case for debugging, Can someone add it to the debugging list ?

Any other solution, I wouldnt be running history.