Bug in windows interface !(

[Mirhodjaev Sherzod]

I can’t use the program completely because it simply doesn’t display all the functions in my window, what should I do?

[gho]

A likely cause could be some high DPI setting of your desktop. Try to set it to 100% or 125% maximum.
What is your operating system? How did you set your desktop?

[Mirhodjaev Sherzod]

Ser I have Windows 11, what about “DPI” I always have it at 100, I think it’s a matter of the resolution of my display, for me it can be a maximum of 1366 x 768, my conclusion is that your program is not optimized for HD displays, now it’s not enough who uses HD displays because Full HD has become much more accessible.

[BEEN_Nath_58]

I do have a Windows 11 with the same 1366x768 resolution, but it just displays fine

[huh]

I believe it must either have something set regarding compatibility in the DxWnd icon shortcut properties or it is not possible for it to have a dpi of 100%. I'm on Win7 with a different resolution, but I have dpi set to 145% and it's more or less fine.

[gho]

I am honestly puzzled. I noted that changing the target computer the GUI sometimes has different measures, but so far the sizes used in the GUI project were satisfactory for all situations.
Taking some measures, I can see that my "Modify" form is sized 489x563 pixels while yours seems 489x503 pixels, so 60 pixels in height were wiped away. But in any case these numbers are far lesser than 1366x768, so I don't think that the screen resolution could be the problem.
More likely it could be something related to the measure units, probably the GUI doesn't have a metric in pixels, but here I need some better investigation, please be patient, I'll try to understand and fix the problem.

[Mirhodjaev Sherzod]

Well, anyway, I think to avoid this problem again, you just need to add a slider for scrolling down, this will allow you to not worry about the size of the window.

[gho]

Adding a scrollbar may have impact on the horizontal space, with the risk of having to add both a vertical and horizontal scrollbar to show the entire form. But I will make some experiment to see if the solution is good enough.
Apart from that, I recall that the "Modify" form is a multi-tabbed form whose size is programmatically built, so MFC could be innocent and the culprit could be the logic that fixes a size for the form. Probably I made some error in the SetWindowSize metric calculations.
A question: is the "Modify" form the only part of DxWnd that gives you troubles? As a reference, you may test some info panel like "View > Palette" or "View > Mouse position".
I made a blind attempt: is this attached GUI behaving better?

[Mirhodjaev Sherzod]

Alas, sir, apparently this GUI patch did not help me, I don’t even know what can help me, I have suspicions that my operating system is involved in this problem - (I’m just guessing, I can’t say for sure.)

[gho]

We can try to see how the situation is.
Can you copy these two small files in a folder, run test.bad and post here its output? It should dump some of your desktop parameters, in particular the values for LOGPIXELSX and LOGPIXELSY that could have something to do with your problem....

[Mirhodjaev Sherzod]

desktop hdc=0xa8010e32
SIZEPALETTE=0
NUMCOLORS=-1
HORZRES=1366
VERTRES=768
HORZSIZE=410
VERTSIZE=230
NUMRESERVED=20
NUMBRUSHES=-1
LOGPIXELSX=96
LOGPIXELSY=96
ASPECTX=36
ASPECTY=36
ASPECTXY=51

[gho]

... though in effect things could be not so simple. From Win8.1+ the DPI depends on the DPI_AWARENESS that can be set per process and even per thread, so maybe it's DxWnd.exe itself that is set for a problematic DPI awareness and values. In short, it's quite a mess!
There must be something that happened on your system (and your system only, since everyone else is happy with the program) that changed the things. Maybe some SHIM, but I need to investigate.

[Mirhodjaev Sherzod]

Yes, that's right sir, I checked something, I installed DXWnd on another Windows 11 and everything worked correctly, most likely the problem is really in my operating system.

[gho]

I suspect that this weird effect could depend on a failure in the GetItemRect function call. If this is true I believe there could be some possible workaround. Are you still interested in fixing the problem in your first machine? If so, I need some logs from an experimental debugging release of the GUI, so I would need your collaboration. Please, let me know ...