[TfcViewerForm_Plugins] in separate ini-file

[bege]

For everyday use I am using the 64-bit donor version. For testing purposes in cases of trouble, I need to transfer settings from XE32 to XE64 and vice versa. But the plugin files are different. Therefore, please, put the [TfcViewerForm_Plugins] settings into a separate ini-file.
Thank you very much.

[BGM]

here! here!

[Free4all]

For everyday use I am using the 64-bit donor version. For testing purposes in cases of trouble, I need to transfer settings from XE32 to XE64 and vice versa. But the plugin files are different. Therefore, please, put the [TfcViewerForm_Plugins] settings into a separate ini-file.
Thank you very much.

Which would be better: separate files or having [TfcViewerForm_Plugins32] and [TfcViewerForm_Plugins64] sections in the existing ini file?

[BGM]

I've been looking at this;
In the end, it might not be worth it.
Most of the time a person uses either the 32bit OR the 64bit application and normally they don't switch back and forth.
Also, most of the plugins come with an .inf file that is just for the plugin itself, and in that file it specifies which version of the plugin is using the actual settings files.
AND if you keep the 32bit and 64bit versions in the same folder you have the problem that you can only have ONE .inf file.

In the end, if you switch from 32 to 64 bit, there's not much to be done, because even if you stored the plugin references for FC, there is the matter of the .inf too.

[Marek]

Which would be better: separate files or having [TfcViewerForm_Plugins32] and [TfcViewerForm_Plugins64] sections in the existing ini file?

Implemented with [TfcViewerForm_Plugins] and [TfcViewerForm_Plugins64]

[bege]

Implemented with [TfcViewerForm_Plugins] and [TfcViewerForm_Plugins64]

Thank you, Marek. How does that work practically? Currently I have XE32 in a subfolder of Program Files (x86) and XE64 in a subfolder of Program Files. Therefor I can use either one, with different path names in the [TfcViewerForm_Plugins] section.
As written in my first post I normally use XE64. If I (un)install a plugin, will XE automatically write it in the correct section? If a problem occurs and I want to test if that also happens in XE32 I will copy freecommander.ini into the XE32 folder what overrides also the plugin section there. Do I have to adapt the XE32 ini-file manually?

[Free4all]

Which would be better: separate files or having [TfcViewerForm_Plugins32] and [TfcViewerForm_Plugins64] sections in the existing ini file?

Implemented with [TfcViewerForm_Plugins] and [TfcViewerForm_Plugins64]

Thanks, Marek. I like that way too.

[Marek]

Thank you, Marek. How does that work practically?

X86 version write/read only the section [TfcViewerForm_Plugins].
X64 version - if the section [TfcViewerForm_Plugins64] does not exists load the plugins from [TfcViewerForm_Plugins] and then write and read the section [TfcViewerForm_Plugins64].

[bege]

X86 version write/read only the section [TfcViewerForm_Plugins].
X64 version - if the section [TfcViewerForm_Plugins64] does not exists load the plugins from [TfcViewerForm_Plugins] and then write and read the section [TfcViewerForm_Plugins64].

So after installing the next XE64 version I must copy the [TfcViewerForm_Plugins]-section from XE32-settings into the XE64-settings. Afterwards I don't need to do anything as long as I don't change anything with the plugins. I can copy the settings forth an back.
If I change plugins in XE32 and copy the settings from XE64 for testing purposes I must copy the [TfcViewerForm_Plugins]-section in XE32-settings before and paste it afterwards. That is not as comfortable as if there were a separate ini-file for the plugins but since I change the plugin-settings seldom that is okay for me.
Thank you, Marek.

[bege]

It is not yet implemented in v691, is that correct?

[joby_toss]

It is implemented in 691: