Font settings problem in alternate user ini

[HBB]

In our company, we use TC over server:

1) TC itself and wincmd.ini are on the server and readonly to users. A shortcut file in each client machine runs TC on the server with same settings.
2) In wincmd.ini, AlternateUserIni key is directed to another user.ini file which is specific and writable for each user.
3) ResolutionSpecific is not currently defined in wincmd.ini and user.ini files (they should be 1 due to the docs).

When a new monitor having new resolution is attached to a client computer, TC creates a new section in user.ini file (e.g., [3840x2160 (8x16)]) and stores the window settings succesfully into that section.

Upto now there is no problem.

But, when the font size is changed, TC does not store the font data into that section. TC tries to write something to the wincmd.ini file (e.g. test in Configution section) and then it fails.

I believe that it should do it. If window positions/sizes can be written, then font data should be written. Because they are kept in same section.

What is my mistake?

Regards

TC8.51a(x64) on Win7(x64)

[MVV]

AFAIK TC uses that test key to test if wincmd.ini is writable. But it seems that it misses the fact that another INI should be modified.

I would prefer too if TC could ignore write errors and continue just like writing was succeed (maybe with an optional single warning message per TC session).

[HBB]

Before I sent post, I thought I was missing somethings.

it seems that it misses the fact that another INI should be modified

It seems a problem in TC.

When I added font data manually into the resolution section, TC accepts it and displays font size as expected.

[ghisler(Author)]

Thanks for your report, I will check it in the debugger. It sounds like TC first tries to write something to wincmd.ini, which fails, so it doesn't try to write the font settings afterwards.

[MVV]

ghisler(Author),
I think it would be much better if TC do all write operations and then optionally report in case of errors (I'm sure INI functions return error if file can't be written).

[HBB]

To Ghisler:

Will you consider the issue in this topic in Version 8.52?

[ghisler(Author)]

I have fixed this for TC 9 already, but it required quite extensive changes to the settings dialog, so I didn't backport it to 8.52. The risk is too high to introduce many new bugs this way, and I want to keep the 8.52 beta test as short as possible so I can proceed with TC 9.