Solved [TC 10.50b1] can no longer use MULTIRENAME with non existant saved setting

[petermad]

In TC 10.00 I could use the command: MULTIRENAME <default> or MULTIRENAME <standard> or with the name of any other non saved setting - and the MultiRename tool would just start with default settings.

In TC 10.50b1 the MultiRename tool still starts with the default setting, but also shows an error: Not found: <default>
Is there a chance that this error message could be suppressed for names like <default> or <standard> or <Voreinstellung> - that is names surrounded with <> to have a way of always opening MRT in default mode.

[ghisler(Author)]

The reason is the new MULTIRENAME=value option - i would be dangerous to start renaming if the settings no longer exist, e.g. because you renamed them.

I could support a specific name, e.g. <default> for all languages plus the localized form for non english languages (e.g. <Voreinstellung> for German). What do you think?

[petermad]

I could support a specific name, e.g. <default> for all languages plus the localized form for non english languages (e.g. <Voreinstellung> for German). What do you think?
Author of Total

Thanks - that would be really nice

[Stefan2]

The reason is the new MULTIRENAME=value option
- i would be dangerous to start renaming if the settings no longer exist, e.g. because you renamed them.

I would expect to see a message in that case, like f.ex.:   [MULTIRENAME: specified setting not found. Action is aborted.]

I could support a specific name, e.g. <default> for all languages
plus the localized form for non english languages (e.g. <Voreinstellung> for German). What do you think?

Me think it is better to use only one name for that feature for all languages,
like "TCdefault", so it is better to explain to various user from around the world.

"he, go and use "MULTIRENAME tcdefault" as button command to start MRT with the default settings"

Else we have to guess what is "default" called in Spanish in case of TCs' MRT


 

[petermad]

17.04.22 Fixed: MULTIRENAME configured_settings: Do not show warning if configured_settings don't exist, only when using = or == autostart options (32/64)

Confirmed fixed in TC 10.50b2

I guess it only makes sense for the non-autostart option - the default setting doesn't do any renaming, so to autostart with the default setting would be unproductive - but not harmful.

[ghisler(Author)]

I guess it only makes sense for the non-autostart option - the default setting doesn't do any renaming, so to autostart with the default setting would be unproductive - but not harmful.

Exactly, that was my conclusion too, that's why I show the error only for autostart now.