On Sat, Apr 18, 2015 at 2:00 AM, Bert Freudenberg <bert at freudenbergs.de>
wrote:

> That's one reason we moved the progress bars to the center of the world.
>

Hi,
Then it is probably the best solution here, too. If direct Sensor access
breaks other code, just doing a fallback to a predictable default seem
better than popping it up the dialog box at a unexpected place

Karl

>
> - Bert -
>
>
> On 17.04.2015, at 16:52, karl ramberg <karlramberg at gmail.com> wrote:
>
> ActiveHands position here is last mouseDown/ mouseUp starting the update
> process.
> If you start update from menu in upper left corner, the mouse position
> will be there.
>
> The information box will pop up in the upper left corner, regardless of
> where the mouse cursor is on screen.
>
> Karl
>
>
>
> On Sat, Apr 18, 2015 at 12:20 AM, Bert Freudenberg <bert at freudenbergs.de>
> wrote:
>
>> On 17.04.2015, at 07:44, Marcel Taeumel <
>> marcel.taeumel at student.hpi.uni-potsdam.de> wrote:
>> >
>> > Well, the problem is that there are no other (mouse) events in the
>> queue at
>> > that moment. That is why #doOneCycle is not sufficient there. Not sure
>> how
>> > many events get cached in the Squeak UI process is busy...
>>
>> Using the active hand's position is the Right Thing. What problems do you
>> see with that?
>>
>> - Bert -
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20150418/8a77be31/attachment-0001.htm