<br><br><div class="gmail_quote">On Thu, Feb 12, 2009 at 10:20 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Michael van der Gulik wrote:<br></div><div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Looking at the implementation of EventSensor and InputSensor, what is the actual history there? In terms of primitives, EventSensor (the "new" class) seems to be more consistent with chapter 29 of the blue book, while the InputSensor (the "old" class) uses undocumented primitives. How did it end up this way?<br>
</blockquote>
<br></div>
InputSensor was first. It used state-based primitive (i.e., primMouseButtons) and was used for a very long time. However, because of its design, it resulted in events being lost (for example, when a mouse down-up transition happens between two polls for input sensor state) so I added the event based primitives. I have never cared much for the blue book so if this is more consistent with chapter 29 it's purely by accident (or perhaps because that's the more sensible way of doing things ;-)<br>
<font color="#888888"></font></blockquote><div><br><br>Another question: using the new event-based primitives, does the VM, underlying window system or OS also queue events on the platform side? I.e. if the EventSensor class doesn't pick up a new event fast enough and queue it, will that event be lost?<br>
</div></div><br>Does this behaviour differ between platforms? Are there any platforms where this could be a problem?<br><br>Gulik.<br clear="all"><br>-- <br><a href="http://people.squeakfoundation.org/person/mikevdg">http://people.squeakfoundation.org/person/mikevdg</a><br>
<a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a><br>