FIXED: Version 4.26 throws an error when loading some batch config files saved by earlier versions
Nevermind! I posted this and then noticed that Kim had JUST NOW released version 4.27 -- which fixes the very issue.
Thanks Kim
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When I go to load some of my trusty old batches, they often throw up an error like:
"TControl.ChangeBounds loop detected uplndex:TUpDown..."
https://postimg.cc/Tp4ZgjrW
The methods will then sometimes (partially) load and sometimes not.
If the .aren contains "methodname" : "add" it triggers for me every time, so far.
Other old batch files seem to load with no problem.
Sample .aren file that triggers the error for me every time:
{
"type" : "preset",
"program" : "Advanced Renamer 4.19",
"version" : 4190000,
"batchmode" : "rename",
"pairrename" : true,
"namecollision.rule" : "fail",
"methods" : [
{
"methodname" : "add",
"description" : "Append file number",
"active" : true,
"position" : "0",
"add" : " aaa",
"backwards" : true,
"applyto" : "name",
"regularexpressions" : false
}
]
}
Regards,
Randy
Thanks Kim
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When I go to load some of my trusty old batches, they often throw up an error like:
"TControl.ChangeBounds loop detected uplndex:TUpDown..."
https://postimg.cc/Tp4ZgjrW
The methods will then sometimes (partially) load and sometimes not.
If the .aren contains "methodname" : "add" it triggers for me every time, so far.
Other old batch files seem to load with no problem.
Sample .aren file that triggers the error for me every time:
{
"type" : "preset",
"program" : "Advanced Renamer 4.19",
"version" : 4190000,
"batchmode" : "rename",
"pairrename" : true,
"namecollision.rule" : "fail",
"methods" : [
{
"methodname" : "add",
"description" : "Append file number",
"active" : true,
"position" : "0",
"add" : " aaa",
"backwards" : true,
"applyto" : "name",
"regularexpressions" : false
}
]
}
Regards,
Randy
Reply to #1:
Yes, I have just released a fix minutes ago. Any method with an up/down edit control can cause this issue, but the position of the method in the list matters. Happens with the Add and Move methods. And Remove method with Remove Type set to Position.
Yes, I have just released a fix minutes ago. Any method with an up/down edit control can cause this issue, but the position of the method in the list matters. Happens with the Add and Move methods. And Remove method with Remove Type set to Position.