Upgrading from 3.0.2 to 3.1.5 causes draws to be at 0.0. #2816
Unanswered
ChadJessup
asked this question in
Q&A
Replies: 1 comment 1 reply
-
For completeness, 3.1.0 gives this exception in the same line of code, but that exception is gone after 3.1.3... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm having a hard time hunting down where the issue is, it could be my code somewhere, but I've spent a good chunk of time trying to hunt this issue down.
If you look at the first image, this is multiple assets draw on top of others - this is for 3.0.2.
After a 3.1.5 upgrade and no other changes, various components are now getting written at 0.0.
My guess is that the minor version bump might have introduced new DrawImage overrides, and I'm now calling different code on accident since I didn't always use named parameters when calling into ImageSharp.
I should note that this first showed up when upgrading from 3.0.2 to 3.1.0 - but due to how input validation changed I had to make code changes to compile, but with 3.1.3 I don't have to do any code changes at all from 3.0.2.
On 3.1.5 Visual Studio is strongly implying I'm calling into this DrawImage override:
In 3.0.2 it looks like I'm calling the same thing (below) - I know in 3.1.0, I had to explicitly try to hit specific overrides because of the validation changes, but I'm trying to minimize changes for this discussion.
Digging through the releases, I have a gut feeling I'm being caught up in one of the DrawImage changes?
#2474
#2673
Any help would be appreciated, this seems like a pretty common code path to be hit, so I'm fairly certain it's an issue on my end, but not sure what's going on.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions