BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Event Timestamps
- Subject: [Discuss] Event Timestamps
- From: kentborg at borg.org (Kent Borg)
- Date: Thu, 12 Feb 2015 09:23:02 -0500
I'm getting old. Back in olden days the Machintosh did a graphical user interface. Many scoffed it wasn't for power users, but the Apple people did some solid work. Much of which is lost to the sands of time. Specifically, doing some playing with pygame (rather cool, I do admit) I am shocked to see that they don't capture the timestamp of the event. God, getting a timestamp is so cheap and it is so small to store with the event (Python makes is to easy to put it in an attribute), yet they don't capture something so basic. They do an event queue, but don't tell me when the events happened. It is one thing to not tell me about a double-click, but to not even give me the data to decide for myself? Stupid! No wonder I see cases where current user interfaces don't seem to even have captured the mouse coordinates with the event, and when things are busy the click is positioned where my mouse is when the software got around to noticing. -kb, the Kent who isn't going to dive into whether OS X is crumbling or not.
- Follow-Ups:
- [Discuss] Event Timestamps
- From: smallm at panix.com (Mike Small)
- [Discuss] Event Timestamps
- Prev by Date: [Discuss] os x = poop?
- Next by Date: [Discuss] Event Timestamps
- Previous by thread: [Discuss] os x = poop?
- Next by thread: [Discuss] Event Timestamps
- Index(es):