Pharo removed the #cursorPoint: selector.results in false or trueInputSensor default cursorPoint:32orInputSensor default cursorPoint:(100@100)so printingCuriosly nowadays the primitive 91 is used for testDisplayDepth,InputSensor>>primCursorLocPut: aPointAndInputSensor>> cursorPoint: aPointLooking at the squeakvm source, there was a primitive for settingthe cursor position:
"Set aPoint to be the current cursor location."
^self primCursorLocPut: aPoint
"If the primitive fails, try again with a rounded point."
<primitive: 91>
^ self primCursorLocPutAgain: aPoint rounded
fails (returns self)
and
InputSensor default cursorPoint:31
2013/3/15 stephane ducasse <stephane.ducasse@free.fr>You can have a look at it on
On Mar 15, 2013, at 9:24 AM, phil@highoctane.be wrote:
> Compared to your speed, I am an anemic snail Stef.
>
> Still, I am very interested in that area of which you showed me
> interesting internals.
>
> Curious about the double dispatch you want to do there. Tell me.
http://smalltalkhub.com/#!/~Pharo/EventModel/packages/EventModel
we should continue to work on it. Fernando is using it since quite a moment :)
Stef
> Phil
>
> 2013/3/15 stephane ducasse <stephane.ducasse@free.fr>:
>>
>> On Mar 14, 2013, at 7:29 PM, phil@highoctane.be wrote:
>>
>>> About basic events, well Apple has internal events and the UIEvents.
>>> The internal events are basic and the UIEvents are user friendly an
>>> dppl can do double dispatch on them. These are two levels: one for the
>>> frameworks, and one for dealing with the low level.
>>>
>>> Anyway, I'd say a proper TextEditorMorph would be a priority over any
>>> event handling code�
>>
>> Alain will start to work on it and Athens will be pushed in 3.0 soon.
>> Now I work on what I can and learn slowly.
>>
>> Stef
>>
>