I just noticed this (version built with new modern x64 c++builder compiler), that control is just showing a bunch of asterisks instead of the text, but if I make a line active (selected) and hover over the link, it shows the text, if I move the cursor off, the text goes back to asterisks?
I retested this here but I could not reproduce such error here.
This was tested with C++Builder 12.2 and the latest version of TMS VCL UI Pack.
If a problem persists, can you send a sample source project with whichi we can reproduce this here?
I noticed older versions didn't display the section headers on Win10. But with the newer modern x64 build under Win10/11 it looks like the pic sent. Under Win7 the text is there but the section header text is ****
More details from the IDE, with no project open, if I load the .exe process (don't run), then choose the run with debugging, all text is fine (the .exe is release version with no debug info), but run without debugging (same as just running .exe by double clicking the .exe) shows the ****** issue.
I know the modern compiler has some bugs with regard to resources, but I don't think your text is in a resource (or is it)? Also, since the older version of compiler still has *** issue with section title text, something is up. We do have over 100 icons (I think it's like 130 or 150) in the program via resources and string table (not too big).
Anyway, if you can't reproduce, send me the test program and I'll see if I can get it to show the issue.
I had a gut feeling that maybe you are loading the text somehow and maybe had to do with ASLR and debug loading changed that .. sure enough it does ... If I disable "Support high-entropy 64-bit address space layout randomization (ASLR)" it works even with basic ASLR is enabled.
Thanks - I found the issue is related ASLR which is an x64 thing only specifically with the option "Support high-entropy 64-bit address space layout randomization (ASLR)", disabling that fixes the problem. I suppose every app will be difference since ASLR is a random thing, but I'm sure as part of a larger app you should see some issues.... Must be related to getting the text from memory areas.
Maybe or maybe not depending on how you implemented it, particularly accessing the text. It does affect your product, you may want to work with them to figure it out.