KeyPath=$ / TC v9.22

[DarkRuleR]

Hi,

With the addition of:

21.01.19 Added: Always look in registry for key if no wincmd.key file is found in the supported locations (32/64)

What is the advantage of the following setting in wincmd.ini?:

KeyPath=$

I have my key in the registry and I was wondering what is best-practice?

Greets,

DR...

[ghisler(Author)]

KeyPath=$ tells TC to look directly in the registry. Therefore a key in the program directory will be ignored. Leaving out KeyPath=$ will make TC look in the program directory and ini file directory first. Only then it will look in the registry.

The advantage is that companies can now distribute the registry key via Windows mechanisms without the need to distribute a wincmd.ini too.

[DarkRuleR]

Thank you for the reply.
So the advantage is an possible (little) speed boost when TC starts?
Because TC don't need to check the program directory.

If checking the registry for an key is part of the startup process is almost seems as an redundant setting?

[ghisler(Author)]

Yes, it should be a bit faster with KeyPath=$, and also tells TC to ignore any wincmd.key file found there.

If checking the registry for an key is part of the startup process is almost seems as an redundant setting?

No, it still tells TC to use the wincmd.key from the registry even if there is a key file.