Modify ↓
Opened 14 years ago
Closed 14 years ago
#1653 closed Bug (Fixed)
Error on Windows Message Codes documentation.
Reported by: | anonymous | Owned by: | Jpm |
---|---|---|---|
Milestone: | 3.3.7.0 | Component: | Documentation |
Version: | 3.3.6.0 | Severity: | None |
Keywords: | Cc: |
Description
Hello, I have noticed a mistake in Windows Message Codes documentation.
On column 'Sorted by Name' we can see 2 WM_KEYLAST WM.
On column 'Sorted by Code' we can see 2 0x0109 WM.
So I think there the 0x0109 WM_KEYLAST WM is enough!
Attachments (0)
Change History (4)
comment:1 Changed 14 years ago by Jpm
- Resolution set to No Bug
- Status changed from new to closed
comment:2 Changed 14 years ago by Jpm
- Resolution No Bug deleted
- Status changed from closed to reopened
sorry I just verify that WM_KEYLAST = WM_UNICHAR. at least it is what I found in MS definition files.
I reopen and fix what it is needed
comment:3 Changed 14 years ago by Jpm
WM_KEYLAST = 0X108 is for Windows 2000 all other systems must use 0x109
comment:4 Changed 14 years ago by Jpm
- Milestone set to 3.3.7.0
- Owner set to Jpm
- Resolution set to Fixed
- Status changed from reopened to closed
Fixed by revision [5855] in version: 3.3.7.0
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Note: See
TracTickets for help on using
tickets.
Both WM_KEYLAST abd WM_UNICHAR are define in MSDN so why to eliminate one of them