from preamble:
"Change Set: EventRecorderPosFix-nk Date: 3 March 2003 Author: Ned Konz
This CS ensures that keyboard events are given positions when replayed from the Event Recorder"!
from preamble:
"Change Set: EventRecorderPosFix-nk Date: 11 July 2003 Author: Ned Konz
This CS ensures that keyboard events are given positions when replayed from the Event Recorder
11 July: cleaned up for MCP approval "!
Just looking at this... is there an example of when a position is needed when replaying a keyboard event? I couldn't come up with an example where it mattered, although I'm sure there must be one.
Also, I assume by "cleaned up for MCP approval" you mean that you've merged the MCP changes with your previous (March 3) changeset? If so, it looks like you overwrote this MCP change: "lastEvent _ nextEvent isMouse ifTrue: [nextEvent]." (this looks like it was just a non-behavior changing simplification though)
- Doug Way
On Friday, July 11, 2003, at 10:48 AM, ned@bike-nomad.com wrote:
from preamble:
"Change Set: EventRecorderPosFix-nk Date: 11 July 2003 Author: Ned Konz
This CS ensures that keyboard events are given positions when replayed from the Event Recorder
11 July: cleaned up for MCP approval "!
<EventRecorderPosFix-nk.cs.gz>
On Saturday 19 July 2003 08:57 pm, Doug Way wrote:
Just looking at this... is there an example of when a position is needed when replaying a keyboard event? I couldn't come up with an example where it mattered, although I'm sure there must be one.
I believe that this is needed for (for instance) popping up menus on the ESC keystrokes. Though this may be covered by keyboard focus. I don't remember.
Also, I assume by "cleaned up for MCP approval" you mean that you've merged the MCP changes with your previous (March 3) changeset? If so, it looks like you overwrote this MCP change: "lastEvent _ nextEvent isMouse ifTrue: [nextEvent]." (this looks like it was just a non-behavior changing simplification though)
Yes, that's a simplification.
squeak-dev@lists.squeakfoundation.org