On Thu, Apr 8, 2010 at 7:51 PM, Romain Robbes <[email protected]>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. > > 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. > Thanks, this bug was really annoying :) Now...I ask completely for ignorance...why you need to wait a timeout ? there is no way to notify from the browser to the oCompletion popup ? so that when it is close, it notifies the rest... > > 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). > > 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
