I also published, in Ocompletion-RomainRobbes.55, a potential fix for this 
issue:

http://code.google.com/p/pharo/issues/detail?id=1678

Cheers,
        Romain

On Apr 8, 2010, at 4:55 PM, Stéphane Ducasse wrote:

> 
> On Apr 8, 2010, at 7:51 PM, Romain Robbes wrote:
> 
>> Dear list,
>> 
>> I just published a version of OCompletion with a possible fix for the bug in 
>> which OCompletion menus would stay on the screen after a browser is closed. 
> 
> Excellent!
> 
>> The issue here is inherited from eCompletion: the menu morph is not a child 
>> of the window, but a top-level morph.
>> To adress this, I implemented a timeout mechanism: if their was no keystroke 
>> in the editor which spawned the menu for the last 5 seconds, the menu will 
>> close automatically. 
>> 
>> You can hence try Ocompletion-RomainRobbes.54 on squeaksource, and tell me 
>> what you think of the solution, or of the length of the timeout (I tried to 
>> stay conservative, maybe something like 3 seconds would work better).
> 
> I'm sure that people will give you feedback. 
> 
>> 
>> Cheers,
>>      Romain
>> 
>> --
>> Romain Robbes
>> http://romain.robb.es
>> [email protected]
>> 
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

--
Romain Robbes
http://romain.robb.es
[email protected]


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to