[squeakland] Found Bug But Not Sure How to Proceed To Fix

[Bob Arning]

Well, here's something you could try...

'From Squeak3.2gamma of 15 January 2002 [latest update: #4743] on 3 
March 2018 at 9:02:03 pm'!

!PasteUpMorph methodsFor: 'misc' stamp: 'raa 3/3/2018 21:00'!
invalidRect: damageRect from: aMorph
         "Clip damage reports to my bounds, since drawing is clipped to 
my bounds."

         self == self outermostWorldMorph
                 ifTrue: [worldState recordDamagedRect: (damageRect 
intersect: self bounds)]
                 ifFalse: [super invalidRect: (self indicateCursor 
ifTrue: [self bounds] ifFalse: [damageRect]) from: aMorph]
! !


On 3/3/18 7:45 PM, Jeremy Landry wrote:
> It was 'lumped in' with my earlier report, but inside 'playfield 
> options' is 'indicate cursor'.  Anything you move or resize with a 
> playfield cursor leaves garbage everywehre.  This was what i was using 
> for testing out warpblt edits.
>
> On Sat, Mar 3, 2018 at 3:23 PM, Bob Arning <arning315 at comcast.net 
> <mailto:arning315 at comcast.net>> wrote:
>
>     Which option is it that makes this appear?
>
>
>     On 3/2/18 1:42 PM, Jeremy Landry wrote:
>>     Whatever code is common that scales morphs is being offset
>>     incorrectly. The first image shows the 'garbage' left behind by
>>     playfield indicator if that option is set.  It seems it was only
>>     tested in 'holders' and thus likely not picked up during
>>     'intended' use. 
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakland.org/pipermail/squeakland/attachments/20180303/d1f8bcd0/attachment.html>