[Cuis-dev] Morphic glitches out/hangs when adding faulty code to drawOn method on morphs that step
Juan Vuletich
juan at cuis.st
Thu Dec 15 14:54:04 PST 2022
Hi All,
I finally could reproduce and understand the problem. Fix is now at GitHub.
Thanks for reporting!
Cheers,
On 12/15/2022 9:50 AM, Juan Vuletich via Cuis-dev wrote:
> Hi Folks,
>
> I guess I need more precise steps to reproduce.
>
> I just fired a fresh Cuis, from an updated repo. Just installed
> updates and opened a Sample09Clock. It works ok. Then I open a browser
> on it (from the halo), went to the drawOn: method and added your line
> Alan. I get a debugger "Instances of SmallFloat64 are not indexable".
> I close the debugger and see the clock displayed now as a red box with
> yellow borders and cross. Image is responsive. I go to the browser and
> correct the method. Then I do World / Debug / Start drawing all again.
> The clock is correctly drawn again.
>
> In short, I see the expected behavior. This means I need enough
> detail, so I can reproduce the problem.
>
> Thanks,
>
>
> On 12/15/2022 6:28 AM, Hilaire Fernandes via Cuis-dev wrote:
>>
>> Hi Alan,
>>
>> Thanks to report! I confirm the issue, even with non stepping morph.
>> It should not behave like that.
>>
>> The expected behavior with faulty code in a #drawOn: method is a
>> broken morph rendered as a red rectangle with yellow diagonals and
>> stepping set in pause, to avoid recurring debugger to pop up I guess.
>> By the way there is the WorldMenu>Debug and Morph halo menus to
>> restart stepping and rendering once the broken code is fixed.
>>
>> It seems the Morph is not detected as broken, and rendering is tried
>> again and again.
>>
>> Juan recently introduced the HybridCanvas to speed up graphics
>> rendering, may be it is related, and a fix should come. I can't help
>> more, sorry.
>>
>> Hilaire
>>
>> Le 15/12/2022 à 07:43, Alan Dao via Cuis-dev a écrit :
>>> I know that the code I've put in is inherently flawed, but my
>>> development process involves experimenting a lot and not always
>>> knowing what I'm doing. Is there something I'm missing when it comes
>>> to not having mistakes break Morphic? Any advice would be appreciated.
>>>
>> --
>> GNU Dr. Geo
>> http://drgeo.eu
>> http://blog.drgeo.eu
>
>
> --
> Juan Vuletich
> cuis.st
> github.com/jvuletich
> researchgate.net/profile/Juan-Vuletich
> independent.academia.edu/JuanVuletich
> patents.justia.com/inventor/juan-manuel-vuletich
> linkedin.com/in/juan-vuletich-75611b3
> twitter.com/JuanVuletich
--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20221215/d5d701d2/attachment.htm>
More information about the Cuis-dev
mailing list