Applies to: desktop apps only
Defines the coordinates of a character cell in a console screen buffer. The origin of the coordinate system (0,0) is at the top, left cell of the buffer.
Syntax
typedef struct _COORD {
SHORT X;
SHORT Y;
} COORD, *PCOORD;
Members
- X
-
The horizontal coordinate or column value. The units depend on the function call.
- Y
-
The vertical coordinate or row value. The units depend on the function call.
Examples
For an example, see Scrolling a Screen Buffer's Contents.
Requirements
|
Minimum supported client | Windows 2000 Professional |
|---|---|
|
Minimum supported server | Windows 2000 Server |
|
Header |
|
See also
- CONSOLE_FONT_INFO
- CONSOLE_SCREEN_BUFFER_INFO
- CONSOLE_SELECTION_INFO
- FillConsoleOutputAttribute
- FillConsoleOutputCharacter
- GetConsoleFontSize
- GetLargestConsoleWindowSize
- MOUSE_EVENT_RECORD
- ReadConsoleOutput
- ReadConsoleOutputAttribute
- ReadConsoleOutputCharacter
- ScrollConsoleScreenBuffer
- SetConsoleCursorPosition
- SetConsoleDisplayMode
- SetConsoleScreenBufferSize
- WINDOW_BUFFER_SIZE_RECORD
- WriteConsoleOutput
- WriteConsoleOutputAttribute
- WriteConsoleOutputCharacter
Send comments about this topic to Microsoft
Build date: 2/3/2012
I found that most of the console api functions can not be used in Visual Basic 6.0, and I try to find out the problem. Then I found all of the api functions with COORD structure can not be used in VB6, including GDI api functions with COORD. Maybe the Declaretion in API Viewer 2004 get wrong?
Public Type COORD
X As Integer
Y As Integer
End Type
and the Declaretion in VC
typedef struct _COORD {
SHORT X;
SHORT Y;
}COORD, *PCOORD;
Are there any problem? The Structure and API functions are useful for us.