Modify ↓
#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 by , on May 29, 2010 at 3:30:38 PM
| Resolution: | → No Bug |
|---|---|
| Status: | new → closed |
comment:2 by , on May 31, 2010 at 7:14:08 AM
| Resolution: | No Bug |
|---|---|
| Status: | closed → 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 by , on May 31, 2010 at 8:26:20 AM
WM_KEYLAST = 0X108 is for Windows 2000 all other systems must use 0x109
comment:4 by , on May 31, 2010 at 8:35:04 AM
| Milestone: | → 3.3.7.0 |
|---|---|
| Owner: | set to |
| Resolution: | → Fixed |
| Status: | reopened → closed |
Fixed by revision [5855] in version: 3.3.7.0
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