Button and submenu icon sizes can be specialized

[HBB]

In TC, window positions/sizes and icon/font sizes in the panels can be adjusted seperately for different screen resolutions. This is very nice/helpfull feature.

But, unfortunately, button sizes and subbar menu icon sizes can't be adjusted for each screen resolution. My suggestion is as follows:

If the keys PopupIconSize, Buttonheight and SmallIconSize (or some others) are found in the current resolution section (e.g. [1920x1080 (8x16)]) in wincmd.ini, they can be considered. Otherwise (if not found) the ones under the section [Buttonbar] is taken into consideration as TC currently does.

Regards

[ghisler(Author)]

The problem is that the button icons are cached in the specific size, so they can't just be changed without re-reading all the buttons.

[HBB]

I know that *.br1 file hold only the icons having same sizes. I can understand that the structure of the *.br1 files can not be modified due to backward compatibility issues.

In old times, most of us had to use a single resolution in monitors such as 800x600 or 1024x768. But now the resolution has been raised to 3840x2160. In near future, we probably are introduced to 16K resolutions. As my own experience, I sometimes need to use three or four monitors having different resolutions in a single day (company machine, meeting machine, home machine, my indispensable netbook, .. etc.).

It would be better that the button bar icons, menus, fonts and all other GUI properties are automatically changed by TC according to the current monitor resolution. wincmd.ini already has a structure to do it easily.

Does a new *.br3 (or other) file, in which multiple icons with multiple sizes are cached, solve the problem? In this case, if *.br3 file exists, TC prefers it. If not exist, *.br1 file is used as TC always does. New age computers and storage media are very fast to read/write files. I don't think TC becomes slower.

I would appreciate if you solve resolution problem.

[ghisler(Author)]

One way to solve it would be to have two separate bar files. But then adding a button to one bar wouldn't update the other...