0005362: BrowserCommentTextMorph causes way too much screen damage!

Notes
(0008060 - 427 - 451 - 451 - 451 - 451 - 451) karl 11-05-06 02:19	I tracked the issue down to SystemWindows>>addPaneSplitters which removes and adds pane splitters when the comment pane is added to the bottom of the browser. I'm not sure how to fix the issue, maybe hiding and showing the pane is better than deleting and reinstalling it. The root cause of the problem seem to be Morph>>privateAddMorph:atIndex: which do a lot of invaliditation that cause a massive redraw when it's sent.

(0008064 - 140 - 140 - 140 - 140 - 140 - 140) karl 11-06-06 22:39	Ok, I think I fixed the issue. Adding morphs needed a position of the morph added otherwise the morph would be added in the top left corner.

(0012373 - 53 - 53 - 53 - 53 - 53 - 53) matthewf 07-15-08 01:49	if this issue is fixed, then where is the resolution?

(0012386 - 386 - 440 - 440 - 440 - 440 - 440) wiz 07-17-08 03:08	Hi Karl, Hi matthew, It seems to me that the BrowserCommentTextMorph and its sometimes pane are the cause of more bugs than you are mentioning here. The cost/benifit is for me to high and my general opinion it that reversion and simplification are called for. What I don't know is how to get a general concensus to do that. Yours in curiosity and service, --Jerome Peace

Relationships