[Pharo-project] Bug reports: 2 of 6:

Stéphane Ducasse stephane.ducasse at inria.fr
Sat Jan 7 18:42:33 CET 2012


I do not think that fork is the solution.

Stef

On Jan 3, 2012, at 2:35 PM, S Krish wrote:

> 
>  ( SimpleButtonMorph new extent: 80 at 60 ; label: 'test' ; on:#click send:
> #value to:[ [UIManager default inform: 'test' ] fork]; color: Color red)
> openInWorld.
> 
> the fork helps.. it simply lets the on:send:to: method continue to finish up the clean up and invoke the mouseUp... 
> 
> It is simply that this target code if it blocks.. it blocks the mouseUp call to the morph and thereby holds the morph as the clickClient...
> 
> On Tue, Jan 3, 2012 at 5:05 PM, Ben Coman <btc at openinworld.com> wrote:
> S Krish wrote:
> 2.  bug with mouseUp not passing through for event handling with
> on:send:to: target...
> 
>  click all over the World and you will keep getting the dialog though you
> are not clicking the morph.
>  #clickClient in MouseClickState holds the morph as the recipient morph for
> clicks.. rather than the modal dialog..
> 
>  ( SimpleButtonMorph new extent: 80 at 60 ; label: 'test' ; on:#click send:
> #value to:[ UIManager default inform: 'test']; color: Color red)
> openInWorld.
> 
>  
> Replicated on:
>  Pharo-1.2.1-OneClick
>  Pharo-1.3-13315-OneCLick
>  Pharo-1.4-14263. Additional observation is that specifically clicking the <OK> button on the dialog does not close it.
> Right-clicking anywhere fixes the behaviour such that clicking <OK> does close the dialog rather than creating a new one.
> 
> 
> 




More information about the Pharo-project mailing list