Issue 3532 in pharo: OB does not allow accepting after deletion only

Status: Accepted
Owner: tudor.girba
Labels: Type-ReportDefect Importance-High Milestone-1.2-DevImage

New issue 3532 by tudor.girba: OB does not allow accepting after deletion  
only
http://code.google.com/p/pharo/issues/detail?id=3532

Pharo image:  
https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/56/artifact/Pharo-1.2/
Virtual machine used: Cog VM 2316
Class browser used (if applicable): OBSystemBrowserAdaptor

Steps to reproduce:
1. Open a browser
2. Select any method
3. Only remove a character
4. Try to accept and it will do nothing

Updates:
        Cc: renggli

Comment #1 on issue 3532 by marianopeck: OB does not allow accepting after  
deletion only
http://code.google.com/p/pharo/issues/detail?id=3532

hehehhe nice find. I could reproduce it.

Comment #2 on issue 3532 by [hidden email]: OB does not allow accepting  
after deletion only
http://code.google.com/p/pharo/issues/detail?id=3532

This seems to come from the following 'bugfix' (comment in  
OBTextMorphEditorWithShout>>backTo:)

        "When backspacing, 2 notifications of the userHasEdited are received.
        This then causes a background process to not terminate correctly.
        The reason for all this is uncertain, but discarding the superfluous  
userHasEdited
        message received while running backTo: seems to cure the problem"

I disabled this fix and do not get any problems... but the reason for the  
fix is not clear.

Updates:
        Status: Closed

Comment #3 on issue 3532 by [hidden email]: OB does not allow accepting  
after deletion only
http://code.google.com/p/pharo/issues/detail?id=3532

Fixed in OBShout-JohanBrichau.12 (in PharoTaskForces)
       
remark: the deleted methods were solving _some bug_ that I do not seem to  
have... (the comments about this are vague and uncertain too). Seems to  
work just fine now.

Lukas feel free to include it in OB (even if we commit it to the TaskForces)