[squeakland] Found Bug But Not Sure How to Proceed To Fix
hakyoku at gmail.com
Fri Mar 2 18:42:41 UTC 2018
Hi, it only appears when scaling a morph. Here is example...it is my
belief (how does one step through code with debugger if there's no bug
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, two pictures show scaling as where the misalignment starts. This
might be why you could not recreate bug; resizing rectangle changes
rectangle morph extent, whereas scaling is a differnet piece of code and
therefore different outcome.
Image included. This works with *anything* scaled.
On Fri, Mar 2, 2018 at 10:20 AM, Bob Arning <arning315 at comcast.net> wrote:
> I tried to recreate your example and could not. How did you create the two
> morphs in your example? Are you certain the read/gray morph does not have
> some transparent pixels along the top and left?
> On 3/2/18 12:50 PM, Jeremy Landry wrote:
> I did a little more digging, just for the record...and it turns out it's
> scaling error. No matter what, scaling offsets morphs by 1 at -1. I'm
> still looking for where this occurs and why. So far, injecting
> intentionally bad values into bordered morph and sketch classes hasn't
> produced any change. It 'feels' like most of that code isn't even used,
> but then again, I might not have genuinely created a new object with that
> code and system might have been giving me what was already in system...
> On Fri, Mar 2, 2018 at 7:15 AM, Bert Freudenberg <bert at freudenbergs.de>
>> That bug tracker is pretty much dead, since all ongoing development moved
>> to squeak.org.
>> The plan was to make a new Etoys release based on the latest Squeak
>> source base, but we have not have enough developer time to make that
>> actually happen.
>> - Bert -
>> On 1 March 2018 at 06:03, Nicco Kunzmann (rambler) <
>> niccokunzmann at rambler.ru> wrote:
>>> I found a bug tracker on the squeakland site:
>>> I think, you can describe the problem there as an issue and hand in the
>>> They may also know how to guide you further if the code base is
>>> somewhere else.
>>> If you have problems there (login, no response), I guess, this mailing
>>> list is one place to ask for help.
>>> On 03/01/2018 03:34 AM, Jeremy Landry wrote:
>>> Hi, while working on a project needing precise alignment of
>>> sketches/bitmaps and rectangles using playfield 'use gridding', it seems
>>> that there's a difference of detected origin.
>>> Here's a screenshot with magnifier showing the discrepency.
>>> I'm quite certain this bug is the one that causes bad redrawing,
>>> especially when showing a cursor move when 'indicate cursor' is activated
>>> in a playfield.
>>> If I correct this bug inside of a project, will it load into an image
>>> where it has not been fixed and be fixed?
>>> I haven't actually fixed the bug yet, but didn't want to waste time on
>>> it if the fix will not travel with the project.
>>> Thanks in advance for any input.
>>> squeakland mailing listsqueakland at lists.squeakland.orghttp://lists.squeakland.org/mailman/listinfo/squeakland
>>> squeakland mailing list
>>> squeakland at lists.squeakland.org
>> squeakland mailing list
>> squeakland at lists.squeakland.org
> squeakland mailing listsqueakland at lists.squeakland.orghttp://lists.squeakland.org/mailman/listinfo/squeakland
> squeakland mailing list
> squeakland at lists.squeakland.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squeakland