Recent posts

#1

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

Last post by NoCforMe - Today at 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.)

#2

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

Last post by zedd151 - Today at 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. 

#3

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

Last post by NoCforMe - Today at 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.

#4

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

Last post by zedd151 - Today at 06:11:19 AM

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

Exactly - Sounds ambiguous.

[coordinates]

#5

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

Last post by NoCforMe - Today at 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.

#6

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

Last post by zedd151 - Today at 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.

#7

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

Last post by NoCforMe - Today at 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.

#8

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

Last post by zedd151 - Today at 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

#9

MasmBasic & the RichMasm IDE / Re: MasmBasic

Last post by jj2007 - Today at 05:39:37 AM

Thanks, Alex

#10

MasmBasic & the RichMasm IDE / Re: MasmBasic

Last post by LordAdef - Today at 04:14:03 AM

Thanks both!

I think Masmbasic is a great project. People under evaluate it due to the extra size. BUT, for large projects this extra size is null. Take the smallest GUI Frameworks around... They size to a minimal of 6mb