INI section redirection with resolution-specific settings

[wanderer]

Is there a way to instruct TC to redirect into another INI file, all newly added sections that contain resolution-specific settings (so, their header is not known in advance)?

[Sir_SiLvA]

Not currently afaik, but I support your suggestion +1

[wanderer]

Not currently afaik

If this is true, can a Mod pls move this post to Suggestions?

[JOUBE]

Is there a way to instruct TC to redirect into another INI file, all newly added sections that contain resolution-specific settings (so, their header is not known in advance)?

Aha, an avid user of virtual machines
The suggestion is not uninteresting. It could definitely relieve the main ini.
+1

Joube

[funkymonk]

support++

[wanderer]

Aha, an avid user of virtual machines

Indeed, that's where the whole thing started from...

[massor]

Redirected or not, I especially want resolution-specific settings for Lister, so...
Support ++

[JOUBE]

Aha, an avid user of virtual machines

Indeed, that's where the whole thing started from...

Do you have tried (within wincmd.ini: Section [Configuration]) in your VMs?

Code: Select all

ResolutionSpecific=0

with the Section

Code: Select all

[AllResolutions]

Joube

[wanderer]

Do you have tried (within wincmd.ini: Section [Configuration]) in your VMs?

Code: Select all

ResolutionSpecific=0

with the Section

Code: Select all

[AllResolutions]

Hmmm... Nope. i've missed that. Thanks, i'll give it a try and see how it goes.

[JOUBE]

...i'll give it a try and see how it goes.

If possible, please report your experiences here. This is useful for others who are looking for this question (especially in combination with VMs) in the forum. Thanks

Joube

[ghisler(Author)]

Have a look at the help, section 4b, click on "wincmd.ini":

1. Global option in section [Configuration]:
AlternateUserIni=<somename.ini>
If present in section [Configuration], it will redirect storing of all user-changeable sections to an alternate ini file (in this example, somename.ini), except for the following sections: [Configuration], [Layout], [Packer], [Confirmation], [Extensions], [Associations], [Shortcuts], [ShortcutsWin], [PackerPlugins], [FileSystemPlugins], [ListerPlugins], [ContentPlugins].

This means that all these new resolutuion-specific sections would be redirected to the specified ini file.
To prevent other sections from being sent there, add the line
RedirectSection=0
to each section you don't want to redirect. This isn't needed for the sections listed above.

[wanderer]

Have a look at the help, section 4b, click on "wincmd.ini"

I'll check it, thanks.

it will redirect storing of all user-changeable sections

Interesting. I'm guessing the "user-changeable sections" are fixed and hard-coded in TC, right? If this mechanism already exists, it might be more interesting to extend it so that the user can massively define which sections he wishes to redirect to which INI.

For instance:

Code: Select all

AlternateUserIni1=<somename1.ini>|[Configuration], [Layout], [Packer]
AlternateUserIni2=<somename2.ini>|[Extensions], [Associations], [Shortcuts]

or perhaps

Code: Select all

AlternateUserIni1=<somename1.ini>
AlternateUserIni1Sections=[Configuration], [Layout], [Packer]
AlternateUserIni2=<somename1.ini>
AlternateUserIni2Sections=[Extensions], [Associations], [Shortcuts]

[petermad]

2wanderer

it might be more interesting to extend it so that the user can massively define which sections he wishes to redirect to which INI.

For this you have the parameter RedirectSection

RedirectSection= Redirect a single section to other ini file. Description here.

I for exampel use:

Spoiler

Code: Select all

[PackerPlugins]
RedirectSection=wincmd_plugins.ini

[PackerPlugins64]
RedirectSection=wincmd_plugins.ini

[FileSystemPlugins]
RedirectSection=wincmd_plugins.ini

[FileSystemPlugins64]
RedirectSection=wincmd_plugins.ini

[ListerPlugins]
RedirectSection=wincmd_plugins.ini

[ListerPlugins64]
RedirectSection=wincmd_plugins.ini

[ContentPlugins]
RedirectSection=wincmd_plugins.ini

[ContentPlugins64]
RedirectSection=wincmd_plugins.ini

[ReplaceIniLocation]
RedirectSection=wincmd_plugins.ini

[DisabledPlugins]
RedirectSection=wincmd_plugins.ini

[rename]
RedirectSection=wincmd_history.ini

[SyncOptions]
RedirectSection=wincmd_history.ini

[Selection]
RedirectSection=wincmd_history.ini

[SearchName]
RedirectSection=wincmd_history.ini

[SearchIn]
RedirectSection=wincmd_history.ini

[SearchText]
RedirectSection=wincmd_history.ini

[RenameTemplates]
RedirectSection=wincmd_history.ini

[RenameSearchFind]
RedirectSection=wincmd_history.ini

[RenameSearchReplace]
RedirectSection=wincmd_history.ini

[left]
RedirectSection=wincmd_history.ini

[right]
RedirectSection=wincmd_history.ini

[lefttabs]
RedirectSection=wincmd_history.ini

[righttabs]
RedirectSection=wincmd_history.ini

[Command line history]
RedirectSection=wincmd_history.ini

[RightHistory]
RedirectSection=wincmd_history.ini

[LeftHistory]
RedirectSection=wincmd_history.ini

[MkDirHistory]
RedirectSection=wincmd_history.ini

[NewFileHistory]
RedirectSection=wincmd_history.ini

[TargetList]
RedirectSection=wincmd_history.ini

[PluginDuplicates]
RedirectSection=wincmd_history.ini

[DirSelection]
RedirectSection=wincmd_history.ini

[activetabs]
RedirectSection=wincmd_history.ini

[LastTracks]
RedirectSection=wincmd_history.ini

[ButtonbarCache]
RedirectSection=wincmd_history.ini

[user]
RedirectSection=wincmd_user.ini

[DirMenu]
RedirectSection=wincmd_user.ini

[AllResolutions]
RedirectSection=wincmd_user.ini

[640x480 (8x16)]
RedirectSection=wincmd_user.ini

[800x600 (8x16)]
RedirectSection=wincmd_user.ini

[1024x768 (8x16)]
RedirectSection=wincmd_user.ini

[1152x864 (8x16)]
RedirectSection=wincmd_user.ini

[1280x960 (8x16)]
RedirectSection=wincmd_user.ini

[1280x1024 (8x16)]
RedirectSection=wincmd_user.ini

[1400x1050 (8x16)]
RedirectSection=wincmd_user.ini

[1920x1080 (8x16)]
RedirectSection=wincmd_user.ini

without using the AlternateUserIni parameter

[wanderer]

For this you have the parameter RedirectSection

Hey petermad. I know, i just proposed a different approach, one in which you have the INI file definition once and then the sections that are redirected. This seems more tidy, now that i think of it though, it seems to have a small chance of being implemented, considering the huge todo list Christian must have in his hands...

[petermad]

2wanderer

i just proposed a different approach,

Not a bad idea - it would make the administration of the redirections easier.