QB64.org Forum

Active Forums => Programs => Topic started by: SpriggsySpriggs on March 26, 2021, 08:45:28 am

Title: Concept: Runtime DLL Calls
Post by: SpriggsySpriggs on March 26, 2021, 08:45:28 am

Recently I pushed a bug fix to GitHub that would allow us to have Windows applications in Vista and higher be DPI aware. I accomplished this using LoadLibrary, a function in the WinAPI that allows for linking a library at runtime rather than at compilation. You then use GetProcAddress to find the address of the function that you are wanting to use from the DLL. You can call the function from that DLL at runtime by calling that address. This allowed me to not have to link the user32.dll library in the _NEWIMAGE function but instead just call it at runtime by finding the DLL and the function. So, since that worked so well, I've made some code here that I think could inspire others who are interested in DLL usage in the Windows environment to try some new things:

Code: C++: [Select]

1. //this code would be saved as runtimecall.h
2. long runtimeCall(LPCSTR dllName, LPCSTR processName){
3.     FARPROC runtime;
4.     HMODULE dllLoad = LoadLibrary(TEXT(dllName));
5.     if(dllLoad != NULL){
6.             runtime = GetProcAddress(dllLoad, processName);
7.             if(NULL != runtime){
8.                 return (runtime) ();
9.                 FreeLibrary(dllLoad);
10.             }
11.             else{
12.                 return -807;
13.                 FreeLibrary(dllLoad);
14.             }
15.     }
16.     else{
17.         return -808;
18.     }
19. }

And an example of the code's usage:

Code: QB64: [Select]

1. Option _Explicit
2.  
3. Declare CustomType Library "runtimecall"
4.     Function runtimeCall& (dllName As String, processName As String)
5. End Declare
6.  
7. Declare Library
8.     Sub SetLastError (ByVal dwErrCode As Long)
9. End Declare
10.  
11. Call SetLastError(85)
12. Print runtimeCall("kernel32.dll", "GetLastError")

 

Obviously, if you want to pass parameters to the functions then you would need to change the function in the header and in the BAS code but this is just a concept showing a familiar WinAPI function being called using runtime linking rather than linking during compilation.

Title: Re: Concept: Runtime DLL Calls
Post by: Pete on March 26, 2021, 11:43:59 am

So it looks like this snippet creates a dll in the local folder, and once created any further iterations of the routine spot it and exit. So to modify the dll you'd have to remove it, right?

This is promising. I like everything about this post except the tag line: "If you're API and you know it clap your hands." The cadence is off by one-syllable. The "you" needs to be removed. Other than that, great coding!

Pete

Title: Re: Concept: Runtime DLL Calls
Post by: SpriggsySpriggs on March 26, 2021, 12:08:59 pm

@Pete This doesn't create a DLL. It simply finds the DLL and then calls the function from that DLL. As for my tagline, you're supposed to pronounce "API" as "appy" (in this case).

Title: Re: Concept: Runtime DLL Calls
Post by: Pete on March 26, 2021, 12:53:34 pm

LOL@API sounds like happy. That one went over my head like a roof on a short bus. Steve(tm)

So something like finding and calling the function in GDI32.DLL for printing a photo, instead of having to call the entire library? Oh, better still, what if I wanted to check the print page number box in the WordPad page setup dialog box, without calling up the dialog box; possible with this approach?

Pete

Title: Re: Concept: Runtime DLL Calls
Post by: SpriggsySpriggs on March 26, 2021, 12:59:22 pm

@Pete I'm not quite sure. It would have to be tailored for each case. In my case, I didn't need any parameters. But yes, you can call a function in GDI32. You'd just need to know the parameters and edit the header and bas accordingly. I'd be happy to assist you when you get to a certain point.

Title: Re: Concept: Runtime DLL Calls
Post by: SpriggsySpriggs on March 26, 2021, 04:51:15 pm

A new version that has taken as much C++ code and moved it to QB64, leaving behind only what can't be done directly in QB64:

Code: C++: [Select]

1. //this would be saved as altruntimecall.h
2. long __runtimeCall(FARPROC funccall){
3.     return (funccall) ();
4. }

Code: QB64: [Select]

1. Option _Explicit
2.  
3. Declare Library
4.     Sub SetLastError (ByVal dwErrCode As Long)
5. End Declare
6.  
7. Call SetLastError(85)
8.  
9. Print runtimeCall("kernel32", "GetLastError")
10.  
11. Function runtimeCall& (dllName As String, processName As String)
12.     Declare CustomType Library
13.         Function LoadLibrary%& (lpLibFileName As String)
14.         Function GetProcAddress%& (ByVal hModule As _Offset, lpProcName As String)
15.         Function FreeLibrary%% (ByVal hLibModule As _Offset)
16.     End Declare
17.     Declare CustomType Library "altruntimecall"
18.         Function dllCall& Alias "__runtimeCall" (ByVal funccall As _Offset)
19.     End Declare
20.     Dim As _Offset runtime 'FARPROC
21.     Dim As _Offset dllLoad: dllLoad = LoadLibrary(dllName)
22.     Dim As _Byte freelib
23.     If dllLoad <> 0 Then
24.         runtime = GetProcAddress(dllLoad, processName)
25.         If 0 <> runtime Then
26.             runtimeCall = dllCall(runtime)
27.             freelib = FreeLibrary(dllLoad)
28.             Exit Function
29.         Else
30.             runtimeCall = -807
31.             freelib = FreeLibrary(dllLoad)
32.             Exit Function
33.         End If
34.     Else
35.         runtimeCall = -808
36.         freelib = FreeLibrary(dllLoad)
37.         Exit Function
38.     End If
39. End Function

Text Only | Text with Attachments