Recent posts

#41

MASM64 SDK / Re: Masm64 SDK ignores "uses"

Last post by zedd - April 21, 2025, 10:09:26 AM

Code Select Expand

Intel(R) Core(TM)2 Duo CPU    E8400  @ 3.00GHz
pushing took 1716 ms
moving  took 2091 ms
pushing took 1794 ms
moving  took 2090 ms
pushing took 1779 ms
moving  took 2090 ms
pushing took 1763 ms
moving  took 1934 ms


Code Select Expand

Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
pushing took 969 ms
moving  took 985 ms
pushing took 953 ms
moving  took 1000 ms
pushing took 968 ms
moving  took 985 ms
pushing took 969 ms
moving  took 984 ms
I like beating my old, slow machine. 

#42

The Campus / Re: Windows 11?

Last post by wjr - April 21, 2025, 08:07:52 AM

Ramon, on the ECPendulum issue, this would be related to the calls to DrawEllipse with the BlackWidth floating point parameter, which with the 64-bit calling convention should be passed through an XMM register.

#43

Windows API / Re: Dialog units vs. screen un...

Last post by NoCforMe - April 20, 2025, 06:56:58 AM

I think the RECT structure fit the purposes of most of those early Windows functions the best.
(In other words, Micro$oft's programmers weren't stupid.)

#44

Windows API / Re: Dialog units vs. screen un...

Last post by zedd - April 20, 2025, 06:22:22 AM

[1] Which I assume is the window size, not the client size.

Exactly - Sounds ambiguous.

Easy enough to find out which it is--just use WinSpy.

No need. I have run my tests.

Why RECT structures anyway? (Rhetorical question) Some functions need x,y,width,height. Which to me is more immediately useful information. Why not a structure for x, y, width, height instead? (Another Rhetorical question btw, no reply needed)

Using a RECT, you'd have to fiddle    around to get the width and height. I guess it's pronounced "wrecked" for a reason. 

#45

Windows API / Re: Dialog units vs. screen un...

Last post by NoCforMe - April 20, 2025, 06:15:31 AM

[1] Which I assume is the window size, not the client size.

Exactly - Sounds ambiguous.

Easy enough to find out which it is--just use WinSpy.

#46

Windows API / Re: Dialog units vs. screen un...

Last post by zedd - April 20, 2025, 06:11:19 AM

[1] Which I assume is the window size, not the client size.

Exactly - Sounds ambiguous.

[coordinates]

#47

Windows API / Re: Dialog units vs. screen un...

Last post by NoCforMe - April 20, 2025, 06:08:07 AM

GetWindowRect() gives you the location of the window in relation to the "real world" (i.e., the desktop)...

For some reason that is what I originally thought that MapDialogRect was supposed to do. I don't remember reading anywhere that it fills in the RECT structure with the client area... if it is the MS docs, I had missed it.

It doesn't do that.
All it does is convert the dialog's coordinates in dialog units to screen units. These can give you the size^[1] of the dialog by subtracting .top from .bottom and .left from .right.

Converts the specified dialog box units to screen units (pixels). The function replaces the coordinates in the specified RECT structure with the converted coordinates, which allows the structure to be used to create a dialog box or position a control within a dialog box.

[1] Which I assume is the window size, not the client size.

#48

Windows API / Re: Dialog units vs. screen un...

Last post by zedd - April 20, 2025, 05:58:48 AM

GetWindowRect() gives you the location of the window in relation to the "real world" (i.e., the desktop)...

For some reason that is what I originally thought that MapDialogRect was supposed to do. I don't remember reading anywhere that it fills in the RECT structure with the client area... if it is the MS docs, I had missed it.

#49

Windows API / Re: Dialog units vs. screen un...

Last post by NoCforMe - April 20, 2025, 05:54:07 AM

Well, keep in mind that GetClientRect() returns the approximately the same dimensions (width & height) as GetWindowRect(), but with the .top and .left elements set to zero. (Obviously GetWindowRect() includes the window's non-client areas as well, like the border, menu bar, etc.)

GetWindowRect() gives you the location of the window in relation to the "real world" (i.e., the desktop), while GetClientRect() just gives you the size of the client area with no location information.

#50

Windows API / Re: Dialog units vs. screen un...

Last post by zedd - April 20, 2025, 05:45:17 AM

Well, Larry, that's the whole point.
The conversion takes dialog units and gives you screen units.
GetClientRect( just confirms this by giving you those same screen units, which shows that the whole thing worked correctly.

Actually I was expecting MapDialogRect to return the screen coordinates of the entire dialog box, its position on the screen and by extension, its size in the left,top,right,bottom members of the structure. 

I was not expecting the client RECT.    but the Window RECT