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
30 lines
491 B
C
30 lines
491 B
C
#pragma once
|
|
|
|
typedef struct _CLIP
|
|
{
|
|
UINT fmt;
|
|
HANDLE hData;
|
|
BOOL fGlobalHandle;
|
|
} CLIP, *PCLIP;
|
|
|
|
UINT APIENTRY
|
|
UserEnumClipboardFormats(UINT uFormat);
|
|
|
|
VOID FASTCALL
|
|
UserClipboardFreeWindow(PWND pWindow);
|
|
|
|
BOOL NTAPI
|
|
UserOpenClipboard(HWND hWnd);
|
|
|
|
BOOL NTAPI
|
|
UserCloseClipboard(VOID);
|
|
|
|
BOOL NTAPI
|
|
UserEmptyClipboard(VOID);
|
|
|
|
VOID NTAPI
|
|
UserEmptyClipboardData(struct _WINSTATION_OBJECT *pWinSta);
|
|
|
|
HANDLE NTAPI
|
|
UserSetClipboardData(UINT fmt, HANDLE hData, PSETCLIPBDATA scd);
|