pdelges

[pattrstorage]'s storenext message is very handy, but would be even more usefull if it would accept a slotname argument like store does.

And if [pattrstorage] would output the slot number used by storenext.

Without this, it's a bit difficult to use storenext and slot names.

Or is there some ugly (or even nice) trick I didn't discover yet?

[pattrstorage]'s storenext message is very handy, but would be even more usefull if it would accept a slotname argument like store does.
And if [pattrstorage] would output the slot number used by storenext.

pattrstorages-storenext-and-slot-names

you could use the "getcurrent" message which outputs the used slot number when storing ( or recalling ) a preset. you can then use the "getslotname" message

Patrick Delges wrote on Tue, 03 November 2009 17:36

you could use the "getcurrent" message which outputs the used slot number when storing ( or recalling ) a preset.  you can then use the "getslotname" message

Patrick Delges wrote on Tue, 03 November 2009 17:36[pattrstorage]'s storenext message is very handy, but would be even more usefull if it would accept a slotname argument like store does.
And if [pattrstorage] would output the slot number used by storenext.

[pattrstorage]'s storenext and slot names