![]() |
#1 |
Human being with feelings
Join Date: Jul 2021
Posts: 7
|
![]()
I've attached a screencap to display the behavior - while the enumeration happens correctly (it properly chooses the number propagation for each duplicate region and starts over from 01 again at a new region name), it displays the word 'number' when it shouldn't.
|
![]() |
![]() |
![]() |
#2 |
Human being with feelings
Join Date: Mar 2007
Posts: 5,091
|
![]()
Hmm, actually I even don't know what it should be like if correct.
As it is now, it seems to be wrong, I think. Mybe someone clever or devs themselves will step-in with some use case example(s)? Because the wildcards help haven't helped much either ![]() |
![]() |
![]() |
![]() |
#3 |
Administrator
Join Date: Mar 2007
Location: NY
Posts: 17,115
|
![]()
Ah, it's a bug that the "number" text is not removed. We'll fix this, but please note that the current workaround to use just "$name" won't work any more after the fix.
|
![]() |
![]() |
![]() |
#4 |
Human being with feelings
Join Date: Mar 2007
Posts: 5,091
|
![]()
OK. Thanks
(BTW, I personally have no problem with the "after-fix" $name wildcard behavior (aka not-working), because I have never used it. So far so good then.) Thank you schwa. |
![]() |
![]() |
![]() |
#5 | |
Human being with feelings
Join Date: Jul 2021
Posts: 7
|
![]() Quote:
Yes, I was looking to use this wildcard in particular because I have many variations of sound assets that get created with the same region name based off their track or parents. Being able to append an enumerated suffix to distinguish between them will be invaluable. |
|
![]() |
![]() |
![]() |
#6 |
Administrator
Join Date: Mar 2007
Location: NY
Posts: 17,115
|
![]()
Well it does work as intended now if you use "$name", the bug is that the string is matched too quickly and the "number" part is not removed.
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|