Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-winehq
Commits
a3c52ef8
Commit
a3c52ef8
authored
Aug 18, 2006
by
Tom Wickline
Committed by
Alexandre Julliard
Aug 18, 2006
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
DEVELOPERS-HINTS: Fix reference in implementing new API calls.
parent
3c71c7cc
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
DEVELOPERS-HINTS
DEVELOPERS-HINTS
+7
-7
No files found.
DEVELOPERS-HINTS
View file @
a3c52ef8
...
...
@@ -277,13 +277,13 @@ uglier, because of the Pascal heritage and the segmented memory model.
All of the Win32 APIs known to Wine are listed in the .spec file of
their corresponding dll. An unimplemented call will look like (from
gdi32.spec)
269 stub PolyBezierTo
@ stub PolyPatBlt
To implement this call, you need to do the following four things.
1. Find the appropriate parameters for the call, and add a prototype to
the correct header file. In this case, that means [include/wingdi.h],
and it might look like
BOOL WINAPI Poly
BezierTo
(HDC, LPCVOID, DWORD);
BOOL WINAPI Poly
PatBlt
(HDC, LPCVOID, DWORD);
If the function has both an ASCII and a Unicode version, you need to
define both and add a #define WINELIB_NAME_AW declaration. See below
for discussion of function naming conventions.
...
...
@@ -294,13 +294,13 @@ to use for the implementation. In Win32, things are simple--everything
is 32-bits. However, the relay code handles pointers and pointers to
strings slightly differently, so you should use 'str' and 'wstr' for
strings, 'ptr' for other pointer types, and 'long' for everything else.
269 stdcall PolyBezierTo(long ptr long) PolyBezierTo
The 'Poly
BezierTo
' at the end of the line is which Wine function to use
@ stdcall PolyPatBlt(long ptr long) PolyPatBlt
The 'Poly
PatBlt
' at the end of the line is which Wine function to use
for the implementation.
3. Implement the function as a stub. Once you add the function to the .spec
file, you must add the function to the Wine source before it will link.
Add a function called 'Poly
BezierTo
' somewhere. Good things to put
Add a function called 'Poly
PatBlt
' somewhere. Good things to put
into a stub:
o a correct prototype, including the WINAPI
o header comments, including full documentation for the function and
...
...
@@ -309,7 +309,7 @@ into a stub:
put in a stub.
/************************************************************
* Poly
BezierTo (GDI32.269)
* Poly
PatBlt (GDI32.@)
*
* Draw many Bezier curves.
*
...
...
@@ -325,7 +325,7 @@ into a stub:
* BUGS
* Unimplemented
*/
BOOL WINAPI Poly
BezierTo
(HDC hdc, LPCVOID p, DWORD count)
BOOL WINAPI Poly
PatBlt
(HDC hdc, LPCVOID p, DWORD count)
{
/* tell the user they've got a substandard implementation */
FIXME("(%x,%p,%d): stub\n", hdc, p, count);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment