mirror of
https://github.com/reactos/reactos.git
synced 2024-09-14 14:51:27 +00:00
e1ef078741
The idea then would be to have the following behaviour (when specifying the following options in the kernel command line): /DEBUGPORT=COMi --> load KDCOM.DLL and use COMi port (i == 1,2,3,4) if possible. /DEBUGPORT=FOO --> load KDFOO.DLL (useful for KDUSB.DLL, KD1394.DLL, KDBAZIS.DLL for VirtualKD, etc...) /DEBUGPORT=ROSDBG:[COMi|SCREEN|FILE|GDB|...] --> load KDROSDBG.DLL which contains the ROS kernel debugger, and use COMi or SCREEN or... as output port. svn path=/branches/kd++/; revision=58883
25 lines
856 B
C
25 lines
856 B
C
#pragma once
|
|
|
|
extern PUSER_MESSAGE_QUEUE gpqForeground;
|
|
extern PUSER_MESSAGE_QUEUE gpqForegroundPrev;
|
|
|
|
/*
|
|
* These functions take the window handles from current message queue.
|
|
*/
|
|
HWND FASTCALL IntGetCaptureWindow(VOID);
|
|
HWND FASTCALL co_UserSetCapture(HWND hWnd);
|
|
BOOL FASTCALL IntReleaseCapture(VOID);
|
|
|
|
/*
|
|
* These functions take the window handles from current thread queue.
|
|
*/
|
|
HWND FASTCALL IntGetThreadFocusWindow(VOID);
|
|
HWND APIENTRY IntGetCapture(VOID);
|
|
HWND FASTCALL UserGetActiveWindow(VOID);
|
|
BOOL FASTCALL co_IntMouseActivateWindow(PWND Window);
|
|
BOOL FASTCALL co_IntSetForegroundWindow(PWND Window);
|
|
BOOL FASTCALL co_IntSetActiveWindow(PWND,HWND *,BOOL,BOOL,BOOL);
|
|
BOOL FASTCALL co_IntSetForegroundWindowMouse(PWND Window);
|
|
BOOL FASTCALL IntLockSetForegroundWindow(UINT uLockCode);
|
|
BOOL FASTCALL IntAllowSetForegroundWindow(DWORD dwProcessId);
|