Change the handling of out-of-bounds canvas - #255
Open
EpicDima wants to merge 1 commit into
Open
Conversation
EpicDima
commented
Nov 18, 2023
| if (widthDiff == 1) { | ||
| rows.forEach { it.add(newBlankPixel) } | ||
| } else { | ||
| rows.forEach { it.addAll(createBlankRow(widthDiff)) } |
Contributor
Author
There was a problem hiding this comment.
I think this is not an ideal solution, because several lists are created, but on the other hand it should not be a hot execution path.
Owner
|
I would like to write tests for this behavior before committing |
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
December 2, 2023 12:01
7a2f4c4 to
8dd3870
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
January 8, 2024 15:04
8dd3870 to
2e592ea
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
January 19, 2024 21:24
2e592ea to
6d1073b
Compare
Owner
|
I haven't forgotten about all these PRs. I'm just busy, but they hover near the top of my "TODO" list and "Feels-bad-about-not-yet-merging" list. |
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
April 20, 2024 16:13
6d1073b to
9df5a80
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
May 16, 2024 08:49
9df5a80 to
94800f1
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
May 29, 2024 08:39
94800f1 to
3be531a
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
3 times, most recently
from
August 19, 2024 16:18
7c53340 to
fa691bb
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
August 21, 2024 12:22
fa691bb to
bafdd41
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
October 24, 2024 01:01
bafdd41 to
0769131
Compare
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
November 16, 2024 23:18
0769131 to
0fed246
Compare
1 task
EpicDima
force-pushed
the
epicdima/change_work_beyond_canvas_borders
branch
from
January 3, 2025 23:39
0fed246 to
9f78f34
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Example from #254
The first picture
The second picture
It seems to be the partial solution for point 5 in #153
Update:
Now this is a simple logic that does not cause crashes, while it allows you to partially draw objects that are partially shifted beyond the border. In the first commit, the canvas expanded automatically, but since this is done in the get method, offset modifier expanded the boundaries, although it should not be as a modifier.