Coloring squares bugs out #315
Comments
|
Yeah, it happened to me too. |
Paalui
added a commit
to Paalui/CellPond
that referenced
this issue
Sep 11, 2024
Bug: TodePond#315 / TodePond#345 / TodePond#309 Didn't read all the code so hope i got it right. When you close a colorchannel it saves the atoms to reuse the gradiets. When opening it again it checks if the old atoms are there and it copies the gradient. But it only checks if the atom is there so when you close the channel before it has drawn all gradients, the gradient is undefined but isGradient is true. I made it that it also copies the isGradient value from the old atom instead of just setting it true.
TodePond
pushed a commit
that referenced
this issue
Nov 11, 2024
* Fixed "doubleclicking" on Colorpicker Bug: #315 / #345 / #309 Didn't read all the code so hope i got it right. When you close a colorchannel it saves the atoms to reuse the gradiets. When opening it again it checks if the old atoms are there and it copies the gradient. But it only checks if the atom is there so when you close the channel before it has drawn all gradients, the gradient is undefined but isGradient is true. I made it that it also copies the isGradient value from the old atom instead of just setting it true. * No sliding set dx and dy to 0 for the missing cases, when a square gets dropped in a paddle. * limit UI size If you make the UI too small it get broken and you have to reset.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seemingly randomly, when editing the colors of a square, the engine bugs out (like in the image above), and you are unable to drag anything, forcing you to restart the page. It's a bit annoying considering there is no saving function.
The text was updated successfully, but these errors were encountered: