Every time the Tc runs, without changes the resolution section is writing accessed

[JOUBE]

Every time the Tc runs, the corresponding resolution section ([1920x1080...] ... ... ...) is writing accessed, although nothing is changed. I have redirected all resolutions and the file constantly shows as changed even though the content is not changed. Please stop the disturbing behavior.

Joube

[ghisler(Author)]

NOT confirmed. TC doesn't save its position on exit. I have tried it, the file doesn't change its last write date.
The section gets written when you use a dialog box which saves its position and size, e.g. the search dialog, or "change user menu". However, it only gets written when something changes. To check this, I have added
[1920x1080 (8x16)]
RedirectSection=1920x1080 (8x16).txt
to the wincmd.ini, and then checked whether the date or time of the file changed.

[JOUBE]

- 9x redirected to wincmd-resolutions.ini.
- The content of the wincmd-resolutions.ini is the same, but the date time has been changed.

Code: Select all

[AllResolutions]
redirectsection=wincmd-resolutions.ini
[1366x768 (10x20)]
redirectsection=wincmd-resolutions.ini
[1920x1080 (10x20)]
redirectsection=wincmd-resolutions.ini
[1600x900 (10x20)]
redirectsection=wincmd-resolutions.ini
[1366x768 (8x16)]
redirectsection=wincmd-resolutions.ini
[1920x1080 (8x16)]
redirectsection=wincmd-resolutions.ini
[1208x680 (8x16)]
redirectsection=wincmd-resolutions.ini
[1600x900 (7x16)]
redirectsection=wincmd-resolutions.ini
[1600x900 (8x16)]
redirectsection=wincmd-resolutions.ini

Code: Select all

[AllResolutions]
...
[1366x768 (10x20)]
...
[1366x768 (8x16)]
...
[1920x1080 (8x16)]
...
[1920x1080 (10x20)]
...
[1600x900 (10x20)]
...
[1208x680 (8x16)]
...
[1600x900 (7x16)]
...
[1600x900 (8x16)]
...

[petermad]

2JOUBE
Does this also happen if all you do is start TC, close TC and start TC again?

[JOUBE]

2JOUBE
Does this also happen if all you do is start TC, close TC and start TC again?

No, but if I use the Sync-Tool it happens. File has same content!

[petermad]

I can confirm that opening and closing the Sync tool without doing anything else updates ini file with redirected sections like: [AllResolutions] and [1920x1080 (8x16)].

The same applies to the Multi-Rename Tool.

But opening and closing all the dialogs in this list does not cause re-writing of the ini file:
Compare*
Connect*
CustColumn*
DriveSel*
MenuChange*
PluginSel*
Print*
Search*
SelectDuplicates*
TreeDlg*

So the problem is restricted to the Sync Tool and the Multi-Rename Tool

[JOUBE]

I can confirm that opening and closing the Sync tool without doing anything else updates ini file with redirected sections like: [AllResolutions] and [1920x1080 (8x16)].

The same applies to the Multi-Rename Tool.

But opening and closing all the dialogs in this list does not cause re-writing of the ini file:
Compare*
Connect*
CustColumn*
DriveSel*
MenuChange*
PluginSel*
Print*
Search*
SelectDuplicates*
TreeDlg*

So the problem is restricted to the Sync Tool and the Multi-Rename Tool

Thanks for testing. It is a annoying problem/bug, as nothing is changed in the affected sections.

[ghisler(Author)]

Thanks, that was very helpful: The only difference between these dialogs is that the two where it gets written save tabstops for the list window. Apparently windows writes that line even when it's not different. I have now changed it to reload the value first, check if it's different, and only write it when it is really different.

[JOUBE]

I have now changed it to reload the value first, check if it's different, and only write it when it is really different.

Thanks, I will test it in the next Release Candidate.

[ghisler(Author)]

This should be fixed in RC6, please test it!

05.11.23 Fixed: Synchronize dirs, multi-rename tool: The tab positions were always written to the settings file even if they didn't change (32/64)

[JOUBE]

This should be fixed in RC6, please test it!

05.11.23 Fixed: Synchronize dirs, multi-rename tool: The tab positions were always written to the settings file even if they didn't change (32/64)

Yes, it is fixed in TC11.02RC6. Many thanks for that! (Tested both TC32 and TC64.)

Joube

[white]

Moderator message from: white » 2023-11-06, 19:02 UTC

Moved to Fixed bugs.

[petermad]

Yes, confirmed fixed in TC 11.02rc6

[JOUBE]

It's really nice that this is fixed.