After the DELPHI dll is injected into the game, the game hides the mouse pointer how it is displayed

The form of the dll must be created with threads and displayed with modals so that it does not disappear.

procedure loadform;, from1);

end;procedure dllmain(dwreason:dword); far;

vardw:dword;

begincase dwreason ofdll_process_attach:

beginbeginthread(nil,0,@loadform,nil,0,dw);

end;dll_process_detach:

beginend;

dll_thread_attach:;

dll_thread_detach:;

end;end;

begindllproc:=@dllmain;

dllmain(dll_process_attach);

end.

Help withstand, help withstand.

Is it that there is a new mouse imported dll mouse and the mouse is gone, or is there no mouse in the first place?

It is estimated that it is caused by an incomplete initialization of your mouse, which cannot be further analyzed due to insufficient information you provided.

You need to ask the question first, not us to find it for you.

Threads are very useful for calling an external program, but if you want to close the external program before allowing the main window to be manipulated, this is easy to achieve with threads.

So it's all about what problem you're trying to solve, not just using it blindly.

The advantage of threading is that multiple threads running together is the advantage.

For example, one thread executes the initializer, another thread counts the number of users, and another thread does other things. You don't see the advantage of being a main thread.

Resource file way on it. You can call dll. directly in a resourceCall the dll in the resource, ** is a bit long, if needed, I'll send you an example.

exe to dll, change the project file, add the output interface function, and recompile it.

What is dll hiding?

The recommended answer is good, and using the resource file will achieve the effect you want.

1. Create your own resource file first. For example, add your cursor to the resource file.

2. Add a compilation indicator to your application3. := loadcursor(hinstance,'Cursor 1'):= loadcursor(hinstance, 'Cursor n'4. All that's left is to call the cursor.

When you load a custom icon, the icon is named with the suffix .cur:

procedure : tobject);

loadcursorfromfile(pchar(extractfilepath( +''));Load custom icons.

end;

You don't even have the function declaration of the dll written by Easy Language, how can you show it?

Looks like someone asked me this question two days ago.

Your form has appeared, but you want to connect to the library, you need to add an event to the created button, or understand that it means that after the dll is injected, F12 will go directly to the library?

You don't inject a direct connection succeed or not?

If it succeeds, the dll connection should be no problem! What do you use to connect? Widgets?

Controls shouldn't work?