Bugs encountered in remote control projects

1 Less parentheses after the function name

Workaround: should be changed to: InitSockEnv()

2 Preprocessor adds security warnings, etc.

_CRT_SECURE_NO_WARNINGS

3 platform bug, replace x64 with x86

4 does not add a bug that converts native byte order to network byte order

htonl is to convert native byte order to network byte order

5 VM network connection bug

6 BUFER_SIZE buffer setting is too small, which causes the interface to freeze and the dialog box cannot move

7 Screen resolution issues and mouse coordinate conversion issues

8 The bug of pressing the Enter key, the solution is to override the OnOk event.

9 Not implemented after static variable declaration

The static member variables in the class are only declared, not implemented.

10 VS bug: the function parameter is wrong, the sixth parameter is wrong, and the result indicates that the first parameter is wrong

11 network multithreading bug

1 Simultaneous triggering of two threads, mouse and screen, thread synchronization and data security

Mouse and monitor conflict.The mouse reply (about 10 bytes) and the monitor reply picture (hundreds of k), the buffer is the same, the picture and the reply bytes affect each other, resulting in a bug that multi-threaded sending messages will conflict, and the mouse and monitor reply willConfused The server can only process one command at a time and may fail to connect.

2 The relationship between size and index is not clear

The relationship between size and index is not clear, resulting in problems with the received data packets and buffer processing, and the display of the monitoring screen cannot be updated normally. The solution: memmove(pBuffer, pBuffer + size, index - size).

12 operator precedence issues

The operator priority may cause bugs in the program.parentheses to prevent errors and make it easier to read

13 memory leak

The memory opened up in the heap area is not released, and vld is introduced to facilitate the troubleshooting of memory leak bugs.Need to include header file #include

14 Registry boot auto-start permission

Mklink lacks a space to specify the System32 path when setting the registry startup permission to automatically start, and is forcibly converted to the SysWOW64 path

When booting up, the permissions of the program follow the startup user
If the permissions of the two are inconsistent, it will cause the program to fail to start
Solution:
[Copy these dlls under System32 or under SysWOW64]
Under System32, mostly 64-bit programs under SysWOW64, mostly 32-bit programs

15 reference header file bug

The function in the header file is referenced multiple times. Solution: Change the definition to a declaration and define it in the source file.In a project, there can only be one definition, and there can be multiple declarations.