summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-12-04 10:17:38 -0500
committerPietro Gagliardi <[email protected]>2014-12-04 10:17:38 -0500
commitad6249422b5a0eb15a3710f54e7e57bedee70597 (patch)
treead69979fedbea4fd011010728d07c31f4c5504a2
parent74f9630bccc1cb9651c9cd3d1ae594d16d4a7823 (diff)
Don't use GetMessagePos(); it returns the same LPARAM format... (and the 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!).
-rw-r--r--wintable/NEWcoord.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/wintable/NEWcoord.h b/wintable/NEWcoord.h
index 6a0fb68..1814e87 100644
--- a/wintable/NEWcoord.h
+++ b/wintable/NEWcoord.h
@@ -13,7 +13,6 @@ static rowcol clientCoordToRowColumn(struct table *t, POINT pt)
}
// same as client coordinates, but stored in a lParam (like the various mouse messages provide)
-// TODO should we use GetMessagePos() instead?
static rowcol lParamToRowColumn(struct table *t, LPARAM lParam)
{
POINT pt;