mirror of
https://github.com/reactos/reactos.git
synced 2024-06-30 09:50:07 +00:00
deae917e9b
Fixes CORE-15558 "AbiWord font listbox should display a specific font only once, but displays each of them many times instead" which regressed by SVN r75491 == 0.4.7-dev-32-gd10c0ec112by porting back the commits: 0.4.12-dev-320-g6e4e5a004cand 0.4.13-dev-107-gae8417fd90to prevent introducing another regression CORE_15785 with the initial fix. and some more addendums to prevent introducing regression CORE_15755 I verified afterwards that all 3 issues: CORE-15558, CORE_15785 and CORE_15755 are in fixed state. Actually I don't really like the resulting code due to the qsort() that it introduces into win32ss/gdi/gdi32/objects/font.c We did not need that at all before 0.4.7-dev-32-gd10c0ec112In case that qsort() would ever reveal any new trouble like reduced performance or stack overflow, we should structurally revert all that context to 0.4.7-dev-31 instead. IntEnumFontFamilies() is called immediately upon process initialization for many applications and the qsorted-list is *huge*, so this indeed could be relevant for performance.
132 lines
4.7 KiB
C
132 lines
4.7 KiB
C
#ifndef WIN32K_NTGDI_BAD_INCLUDED
|
|
#define WIN32K_NTGDI_BAD_INCLUDED
|
|
|
|
/*
|
|
*
|
|
* If you want to help, please read this:
|
|
*
|
|
* This file contains NtGdi APIs which are specific to ROS, including
|
|
* a short comment describing the solution on how to use the actual NtGdi
|
|
* call documented in ntgdi.h. Here are the main cases and information on
|
|
* how to remove them from this header.
|
|
*
|
|
* - Simple rename. This deals with an API simply having a different name,
|
|
* with absolutely no other changes needed.
|
|
* - Rename and new parameters. This deals with a case similar to the one
|
|
* above, except that new parameters have now
|
|
* been added. This is also usually extremly
|
|
* simple to fix. Either pass the right params
|
|
* or pass null/0 values that you ignore.
|
|
* - Rename and new structure. This is similar to the above, except that the
|
|
* information is now passed in a differently
|
|
* named and organized structure. Ask Alex for
|
|
* the structure you need and he will add it to
|
|
* ntgdityp.h
|
|
* - Rename and different semantics. Similar to the previous examples, except
|
|
* that parameters have usually been removed
|
|
* or need to be converted in user-mode in
|
|
* one form of another.
|
|
* - Does not exist: user-mode. This means that the API can be fully done in
|
|
* user mode. In 80% of cases, our API was already
|
|
* returning NOT_IMPLEMENTED in kernel-mode, so
|
|
* the work to be done is minimal. A good example
|
|
* are the ICM and Metafile APIs, which can simply
|
|
* be removed and added into gdi32.
|
|
* - Does not exist: GDI Shared Objects. This is by far the hardest case. This
|
|
* class cannot be fixed until ReactOS
|
|
* has a working Shared GDI Object table
|
|
* and a DC_ATTR structure in which the
|
|
* attributes, selection and deletion of
|
|
* objects can be quickly done from user-
|
|
* mode without requiring a kernel mode
|
|
* call.
|
|
*/
|
|
/* Should be using ENUMFONTDATAW */
|
|
typedef struct tagFONTFAMILYINFO
|
|
{
|
|
ENUMLOGFONTEXW EnumLogFontEx;
|
|
NEWTEXTMETRICEXW NewTextMetricEx;
|
|
DWORD FontType;
|
|
} FONTFAMILYINFO, *PFONTFAMILYINFO;
|
|
|
|
/* Should be using NtGdiEnumFontChunk */
|
|
LONG
|
|
NTAPI
|
|
NtGdiGetFontFamilyInfo(
|
|
HDC Dc,
|
|
const LOGFONTW *LogFont,
|
|
PFONTFAMILYINFO Info,
|
|
LPLONG UnsafeInfoCount);
|
|
|
|
/* Use NtGdiGetDCPoint with GdiGetViewPortExt */
|
|
BOOL APIENTRY NtGdiGetViewportExtEx(HDC hDC, LPSIZE viewportExt);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL APIENTRY NtGdiGetViewportOrgEx(HDC hDC, LPPOINT viewportOrg);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL APIENTRY NtGdiGetWindowExtEx(HDC hDC, LPSIZE windowExt);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL APIENTRY NtGdiGetWindowOrgEx(HDC hDC, LPPOINT windowOrg);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL
|
|
APIENTRY
|
|
NtGdiOffsetViewportOrgEx (
|
|
HDC hDC,
|
|
int XOffset,
|
|
int YOffset,
|
|
LPPOINT Point
|
|
);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL
|
|
APIENTRY
|
|
NtGdiOffsetWindowOrgEx (
|
|
HDC hDC,
|
|
int XOffset,
|
|
int YOffset,
|
|
LPPOINT Point
|
|
);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL
|
|
APIENTRY
|
|
NtGdiSetViewportOrgEx (
|
|
HDC hDC,
|
|
int X,
|
|
int Y,
|
|
LPPOINT Point
|
|
);
|
|
|
|
/* Needs to be done in user-mode. */
|
|
BOOL
|
|
APIENTRY
|
|
NtGdiSetWindowOrgEx (
|
|
HDC hDC,
|
|
int X,
|
|
int Y,
|
|
LPPOINT Point
|
|
);
|
|
|
|
#endif /* WIN32K_NTGDI_BAD_INCLUDED */
|
|
|
|
|
|
/* Follow thing need be rewriten
|
|
*
|
|
* Opengl icd are complete hacked in reactos and are using own way, this need be rewriten and be setup with the correct syscall
|
|
* and the opengl32 shall using correct syscall to optain then driver interface or using the correct version in gdi32.
|
|
* it mean whole icd are hacked in frist place and need be rewtiten from scrash. and it need enum the opengl correct way and
|
|
* export the driver correct
|
|
*
|
|
* DirectX aka ReactX alot api that have been implement in reactos win32k for ReactX shall move to a file call dxg.sys
|
|
* there from it will really doing the stuff. And we should setup loading of dxg.sys
|
|
*
|
|
* The Init of Gdi subsystem shall move into NtGdiInit()
|
|
*
|
|
* The Init of spooler are done in NtGdiInitSpool()
|
|
*
|
|
* The Init of the User subsystem shall move into NtUserInit()
|
|
*/
|