IML target_Patch

[23fx23]

Id like to make a subpatch that use IML locally to set some named module values. (an encoder)

ie in the subpatch there is a module like a knob and it's named 'POT'. so i use 'set_target_patch sender_patch', to set it's value . and it's ok.

now i wanna go up to parent patch, duplicate this subpatch to get more pots. I was thinking that renaming differently the subpatchs, would
make the item activate when concerned, as iml trig locally a "set_target_sender', so according to it's name, but if i move one of all pots, only one will move ie, the second, and whatever wich one i move it will move the second, the changing target patch doesn't operate, but i can see it changing in the console, i don't catch ..

ie
Set_target_patch A
Set Value POT 1 1
Set_target_patch B
Set Value POT 1 1

but only /B/Pot 1 1 will move, even if i move the one from subpatch A.

I ve notice that all subpatch clones (renamed) access so same locally named item, ie 'POT',
but if I change each names of pots, then it work. but it implies going to the script and renaming items on
each creations,subpatch. i wished there could be a solution using patch selection by it's name, i must miss something..

don't know if im clear, if some see what i mean.. in other wordz

is it possible to make some clones subpatches that use iml locally with same named inside items, if thoses subpatchs are then named differently, or is there something special to do? i don't manage. arf

ive made a very simple patch example of what i don't understand:
dlike each button reset each concerned fader:
the patch here

[Floego]

I tested you workspace. It happened the same to me.
Why don't you bring the usinemsg to the main patch? with usinemsg you could even rename the Pot, using, for example:

SET_TARGET_PATCH SENDER_PATCH
SET_TARGET_PATCH fader_2
RENAME_MODULE A B
SET_VALUE B 1 0

All this without opening each subpatch?
It is just an idea, not a solution.

[23fx23]

yeah thanks floego. my subpatchs will be more complexes, ideally i wanted them to be the same for easy cloning, and "independant" then via renaming, but maybe I got to deal with a message on parent patch than rename each module
first, you're right... might be a good workaround.

[senso]

I'll take a look, possibly a bug

[senso]

I confirm, It's a bug, will be fixed in the next release.