Can't compile simple WinApi call

[DiffrenzyKeymaster]

I’m trying to get this to compile, but get :

C:/Monkey2-v1.1.06/tmp/untitled2.buildv1.1.06/windows_debug/src/untitled2_untitled2.cpp:19:3: error: ‘WINRECT__’ was not declared in this scope

WINRECT__* l_parentrect{};

^~~~~~~~~

C:/Monkey2-v1.1.06/tmp/untitled2.buildv1.1.06/windows_debug/src/untitled2_untitled2.cpp:19:14: error: ‘l_parentrect’ was not declared in this scope

WINRECT__* l_parentrect{};

 

Monkey

#Import "<libuser32.a>" #Import "<std>" #Import "<windows.h>" #Import "<std>" #Import "<mojo>" Using mojo.. Using std.. Extern Alias LPCTSTR:CString Struct HWND__ End Alias HWND:HWND__ Ptr Struct WINRECT__ Field left:Int Field top:Int Field right:Int Field bottom:Int End Alias LPRECT:WINRECT__ Ptr Extern Function GetClientRect:Bool(in:HWND,out:LPRECT) Function GetCommandLineW:LPCTSTR() Function MessageBoxA:Int (hWnd:HWND, lpText:CString, lpCaption:CString, uType:Int) Public Function Main() Local phwnd:HWND ' dummy Local parentrect:LPRECT GetClientRect(phwnd, parentrect) End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

#Import "<libuser32.a>" #Import "<std>"   #Import "<windows.h>" #Import "<std>" #Import "<mojo>"   Using mojo.. Using std..    Extern   Alias LPCTSTR:CString   Struct HWND__ End Alias HWND:HWND__ Ptr     Struct WINRECT__   Field left:Int   Field top:Int   Field right:Int   Field bottom:Int End Alias LPRECT:WINRECT__ Ptr Extern   Function GetClientRect:Bool(in:HWND,out:LPRECT) Function GetCommandLineW:LPCTSTR() Function MessageBoxA:Int (hWnd:HWND, lpText:CString, lpCaption:CString, uType:Int) Public     Function Main() Local phwnd:HWND ' dummy Local parentrect:LPRECT   GetClientRect(phwnd, parentrect) End

[Mark SiblyKeymaster]

Never heard of struct WINDRECT__ before – try plain old RECT instead, works fine here:

https://msdn.microsoft.com/en-us/library/windows/desktop/dd162897(v=vs.85).aspx

Possibly time to start a win32 module?

[DiffrenzyKeymaster]

I just called it something, does the naming of the struct matter?

A Win32 module seems like a good idea.

[DiffrenzyKeymaster]

[EDIT]

Got it compiling by using RECT (no underscores), don’t know why though. I’m thinking the struct needs to match the naming in windows.h or… ?

Monkey

#Import "<libuser32.a>" #Import "<std>" #Import "<windows.h>" #Import "<std>" #Import "<mojo>" Using mojo.. Using std.. Extern Alias LPCTSTR:CString Struct HWND__ End Alias HWND:HWND__ Ptr Struct RECT Field left:LONG Field top:LONG Field right:LONG Field bottom:LONG End Function GetClientRect:Bool(in:HWND,out:RECT Ptr) Function GetCommandLineW:LPCTSTR() Function MessageBoxA:Int (hWnd:HWND, lpText:CString, lpCaption:CString, uType:Int) Public Function Main() Local phwnd:HWND ' dummy Local parentrect:RECT GetClientRect(phwnd, Varptr parentrect) End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

#Import "<libuser32.a>" #Import "<std>"   #Import "<windows.h>" #Import "<std>" #Import "<mojo>"   Using mojo.. Using std..    Extern   Alias LPCTSTR:CString   Struct HWND__ End Alias HWND:HWND__ Ptr     Struct RECT   Field left:LONG   Field top:LONG   Field right:LONG   Field bottom:LONG End   Function GetClientRect:Bool(in:HWND,out:RECT Ptr) Function GetCommandLineW:LPCTSTR() Function MessageBoxA:Int (hWnd:HWND, lpText:CString, lpCaption:CString, uType:Int) Public   Function Main() Local phwnd:HWND ' dummy Local parentrect:RECT   GetClientRect(phwnd, Varptr parentrect) End

[Mark SiblyKeymaster]

I’m thinking the struct needs to match the naming in windows.h or… ?

Yes, defnitely, that’s why WINRECT__ didn’t work, there’s no such thing in windows.h.

So yes, the naming is important, the compiler has to be able to find the definition of struct RECT or whatever it is somewhere.

[DiffrenzyKeymaster]

ok, thanks got it now.

I don’t get why some things are written:

Struct HWND__
End
Alias HWND:HWND__ Ptr

and some

struct RECT

and where to look it up though.

[Mark SiblyKeymaster]

> I don’t get why some things are written:

Mainly because this is how it’s written in the .h files, ie: the equivalent ‘c’ is probably something like:

Monkey

struct HWND__{ }; typdef HWND__ *HWND; typedef struct _RECT{ DWORD l,t,r,b; //no idea about this actually... }RECT;

1 2 3 4 5 6 7

struct HWND__{ }; typdef HWND__ *HWND;   typedef struct _RECT{    DWORD l,t,r,b; //no idea about this actually... }RECT;

It’s wildly inconsistent, but that’s how windows is written and it has it’s own sort of logic.

The goal here is to come up with monkey2 code that matches the meaning of the actual ‘c’ code in windows.h so the compiler accepts the output monkey code.

Where to look it all up is a bit tricky. Header files are a good start, and googling ‘msdn HWND’ etc still works pretty well a lot of the time. I should be able to do most the HWND etc type stuff myself, and after that it’s just a matter of entering the APIs.

This is kind of one level of abstraction away from how blitzmax worked, where you had to declare structs very precisely so that struct byte sizes and field offsets were exactly right or all hell would break lose at the binary level. With monkey2, you really just have to get types and names right or things break at the compiler level instead!

[DiffrenzyKeymaster]

Thanks for explaing. I see now that I need only write the names of constants, and then the values are automaticly picked up, very handy like in:

Const WS_CHILD:Int

[Mark SiblyKeymaster]

Yes, the values of these consts are already defined in windows.h!

[Author]

Posts