Bug 186 - Total mouse movements should not be measured in pixels
Status:
RESOLVED FIXED
Component:
GUI :: gtkmm
Version:
0.1.0
Hardware:
All All
Importance:
P3 normal
Target Milestone:
---
Assignee:
Raymond Penners
URL:
Depends on:
Blocks:
Reported:
Feb 21 2003 00:00:29 UTC
by:
Raymond Penners
Modified:
Feb 26 2003 01:33:14 UTC
WhoWhenWhatRemovedAdded
Raymond PennersFeb 21 2003 07:58:48 UTCassigned_toRob CaelersRaymond Penners
Raymond PennersFeb 21 2003 10:16:15 UTCstatusNEWRESOLVED
resolutionFIXED
Description
Raymond Penners  Feb 21 2003 00:00:29 UTC
Pixels don't mean much to ordinary users.
Use meters/inches instead. This can be done by obtaining the monitor DPI...
Comment 1
Raymond Penners  Feb 21 2003 07:58:48 UTC
This is relatively easy to do using gdk_screen_width_mm().
Comment 2
Raymond Penners  Feb 21 2003 10:16:15 UTC
Now displays in meters.
Comment 3
Kees-Jan Dijkzeul  Feb 26 2003 00:42:01 UTC
I'm not sure I agree here.
Meters don't mean much either, since these are meters the mouse pointer moves
over the screen. The actual value of interest would be the number of meters you
actually move your mouse. This also depends on the mouses speed and acceleration
settings.

So I would argue that pixels mean exactly as much as meters: It's some value
that is proportional to the amount of distance the mouse actually travelled
(assuming acceleration is turned of). Hence, I would be in favor of displaying
mouse distance in pixels, since this makes it very clear that we are not talking
about the distance the mouse travelled, only the mouse pointer.
Comment 4
Raymond Penners  Feb 26 2003 01:33:14 UTC
We're dealing with ordinary users here. For them, meters really mean more then
pixels because they can relate that to something that has a meaning in real
life. For example, my girlfriend (err, wife) does not know how many pixels a
screen is. For her, 143214 pixels per day has no meaning at all, none
whatsoever. Meters she can at least relate to, even if it is only about screen
meters instead of mousepad meters.