microsoft / microsoft/win32metadata
DEVMODE struct
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 149
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 4
Description
PTConvertPrintTicketToDevMode and DocumentProperties generate different struct (DEVMODEA vs DEVMODEW).
It will be good to align this.
Here is sample from CSWin32
internal static unsafe winmdroot.Foundation.HRESULT PTConvertPrintTicketToDevMode(SafeHandle hProvider, winmdroot.System.Com.IStream pPrintTicket, winmdroot.Graphics.Printing.PrintTicket.EDefaultDevmodeType baseDevmodeType, winmdroot.Graphics.Printing.PrintTicket.EPrintTicketScope scope, out uint pcbDevmode, out winmdroot.Graphics.Gdi.DEVMODEA* ppDevmode)
internal static unsafe int DocumentProperties([Optional] winmdroot.Foundation.HWND hWnd, SafeHandle hPrinter, winmdroot.Foundation.PWSTR pDeviceName, [Optional] winmdroot.Graphics.Gdi.DEVMODEW? pDevModeInput, uint fMode)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the metadata for PTConvertPrintTicketToDevMode and DocumentProperties with the CSWin32-generated signatures shown in the issue. Trace how each DEVMODE parameter is defined and generated, then verify that both APIs produce the intended, aligned struct type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100