The row data for the AttackType column doesn't seem to be appearing about advancedcombattracker HOT 8 OPEN

Similarly, the 'Victim' field was affected. While 'You' is visible, '木人' is not displayed, indicating a high possibility of a Japanese language-related issue.

from advancedcombattracker.

Likely this is a font rendering problem in GDI+.

Could you export a *.act file and attach it here for me to test with?

Also, I need to know what font you're currently using. The least error prone way is to get it from the config file line. It will look something like the following near the bottom of the file:

<FontColorControl Name="fccDataGrid" ForeColor="-1447447" BackColor="-15790319" Font="Calibri Light" Style="Regular" Size="9.75" />

It looks like you have some custom DPI scaling happening, but I don't think that's the issue.

from advancedcombattracker.

I couldn't figure out how to export the *.act file. However, upon hearing about the DPI issue, I tried the following, and the problem was resolved. Thank you!

Compatibility of Advanced Combat Tracker.exe → Change DPI settings to High → Set 'Override high DPI scaling behavior' to 'Application' as shown in the screenshot, under 'Scaling performed by:'

Reference information:
・ACT settings remain at their default configuration. (Fonts and colors have all been reset)
・OS is Windows 11 23H2 (OS Build 22631.3007)
・The monitor used is a 4K display.

from advancedcombattracker.

It would have been the following:

I wonder why the DPI scaling would make things invisible, though. I noticed that the Latin letters were rather too big for the rows, which made me think of DPI scaling to begin with... I wonder if katakana/kanji needed more room to render vertically at that font size... and the layout decided to push it to another line that didn't show up?

from advancedcombattracker.

The *.act file is here. Does this seem sufficient for reproduction?

MultipleEncounters.zip

from advancedcombattracker.

This problem appears to be specific to running Hojoring plugins. They load the WPF UI framework into ACT which overrides how DPI settings are handled. When DPI settings are at default, this issue appears. Overriding DPI settings like you have done will fix this issue. Not using Hojoring will also fix this issue no matter what DPI settings are used.

Maybe having ACT include DPI aware overrides will help, but I'm concerned this will change how ACT looks for some people when they were not expecting it.

from advancedcombattracker.

I appreciate the investigation. I do have Hojoring installed, so that's probably the cause. As long as I know the reason, it's fine!

from advancedcombattracker.