I am trying to make a system for dynamically creating modulators for a synth, so far I have it so that each time "LFO" is selected from a popup, a new one is created, with an argument one bigger than the last, (arg used to send~ $1-LFO etc). The problem comes when I have deleted an LFO, and create another one, it keeps adding to the last number, not "filling the gap" for instance:

when i have in existence:
LFO 1
LFO 2

LFO 4

the next LFO created is "LFO 5", not "LFO 3". It works fine if you remove the last LFO from the patch.

I am currently exploring list management but it is quite complicated. I feel it's so close but just out of reach.

I would also like to find a way to delete these LFO objects dynamically instead of entering edit mode.
the closest I have come is:
[find LFO, cut(

but it seems to cut each object (even messages) containing the symbol "LFO", and I cannot seem to "point" it to the one I want to delete!

In both cases, I'm sure im over complicating, but have learnt enough in my own process of exploration now and need some guidance!

patch attached, with LFO included Modulator w LFO included.zip

I might not be following you correctly, but you might be able to use [closebang] to eg. reset a counter in the parent patch when the abstraction is deleted.

Regarding dynamic deleting, the best option I'm aware of is [iemguts/canvasdelete]. You might need to use it in conjunction with [iemguts/canvasindex] in order to identify the right object to delete. This can be tricky...

thanks for the swift reply. I shall try these out ! btw I have spent some serious hours on this forum and your suggestions for otheres have been invaluable so thanks for them too!

hey,
you can use the find, cut message if you search for arguments like "1-LFO" instead of "LFO". but in this case you have to make shure that there is no "1-LFO" stored in the obj-creation message, otherwise pd will crash. and you might have to replace your send and receive args inside the LFO abstraction.
anyway, MODULATOR_delete.pd maybe this brings you one step forward

@LiamG said:

I might not be following you correctly, but you might be able to use [closebang] to eg. reset a counter in the parent patch when the abstraction is deleted.

Regarding dynamic deleting, the best option I'm aware of is [iemguts/canvasdelete]. You might need to use it in conjunction with [iemguts/canvasindex] in order to identify the right object to delete. This can be tricky...

Thanks LiamG, this works a treat, a combination of those three does exactly what i need, and has given me some ideas about another patch.

@solipp said:

hey,
you can use the find, cut message if you search for arguments like "1-LFO" instead of "LFO". but in this case you have to make shure that there is no "1-LFO" stored in the obj-creation message, otherwise pd will crash. and you might have to replace your send and receive args inside the LFO abstraction.
anyway, MODULATOR_delete.pd maybe this brings you one step forward

And thanks solipp, that's also really handy to know, but seeing as Liam's solution gets rid of about half my patch im going to go with that on this one. thanks for taking the time to edit my patch. much appreciated!

D