| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
implemented).
|
|
|
|
dummy data).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
will be slowly readded, but in a different order) and fixed compilation errors (and some warnings).
|
|
|
|
|
|
|
|
|
|
POINT in MSG is in screen coordinates, which means we need to call the potentially-erroring ScreenToClient(), and /even then/ we would need to hack up the message pump to get that point out, which is not guaranteed if someone takes our Table code and uses it in their own Windows program, or if I even export this Table for such use!).
|
|
coordinate system management.
|
|
|
|
|
|
|
|
WM_USER just in case we ever get dialog manager messages (which are the first few WM_USER messages because technically they belong to WC_DIALOG).
|
|
|
|
|
|
respective files.
|
|
move the public-facing API code (namely the WM_SETFONT handler) there we can use functions defined later.
|
|
|
|
|
|
|
|
|
|
|
|
Added basic window example. Thanks @adamar.
|
|
|
|
Thanks to github user @infogulch.
|
|
|
|
what) to the Windows Table main() to specify using the lfMessageFont, for vertical centering testing purposes.
|
|
|
