Forum - Public Discussion and Support
https://www.ghisler.ch/board/
If this is true, can a Mod pls move this post to Suggestions?
Aha, an avid user of virtual machineswanderer wrote: 2023-06-16, 09:59 UTC 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)?
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=0Code: Select all
[AllResolutions]Hmmm... Nope. i've missed that. Thanks, i'll give it a try and see how it goes.JOUBE wrote: 2023-06-21, 01:47 UTCDo you have tried (within wincmd.ini: Section [Configuration]) in your VMs?with the SectionCode: Select all
ResolutionSpecific=0Code: Select all
[AllResolutions]
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
This means that all these new resolutuion-specific sections would be redirected to the specified ini file.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].
I'll check it, thanks.ghisler(Author) wrote: 2023-06-21, 08:31 UTCHave a look at the help, section 4b, click on "wincmd.ini"
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.ghisler(Author) wrote: 2023-06-21, 08:31 UTCit will redirect storing of all user-changeable sections
Code: Select all
AlternateUserIni1=<somename1.ini>|[Configuration], [Layout], [Packer]
AlternateUserIni2=<somename2.ini>|[Extensions], [Associations], [Shortcuts]Code: Select all
AlternateUserIni1=<somename1.ini>
AlternateUserIni1Sections=[Configuration], [Layout], [Packer]
AlternateUserIni2=<somename1.ini>
AlternateUserIni2Sections=[Extensions], [Associations], [Shortcuts]For this you have the parameter RedirectSectionit might be more interesting to extend it so that the user can massively define which sections he wishes to redirect to which INI.
I for exampel use:Help wrote:RedirectSection= Redirect a single section to other ini file. Description here.
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.iniHey 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...
Not a bad idea - it would make the administration of the redirections easier.i just proposed a different approach,