New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ebitenutil: DebugPrint ignoring image origin #2977
Comments
I mean, I'm unsure of the exact desired behaviors, in some cases |
I feel like this is an expected behavior. |
Yes, I think it's for the same reason that if you do edit: maybe this is not really desirable (?) but at least it seems consistent with the other API behaviours regarding sub-images |
I mean, the documentation says:
There are two possible interpretations of this:
I'm fine with current behavior being the desired one, but I don't think the most reasonable interpretation of the function description matches the current behavior. Regarding Zyko's comment, // The default (zero) value is identity, which draws the image at (0, 0). So, I think there is no parallel with |
Ok so I'd like to update the documentation side. |
Ebitengine Version
v2.7.2
Operating System
Go Version (
go version
)go1.22.2
What steps will reproduce the problem?
Using
ebitenutil.DebugPrint()
on an image with non-zero origin.What is the expected result?
Text drawing on the top left.
What happens instead?
Text being cut or not visible.
Anything else you feel useful to add?
E.g., see https://github.com/hajimehoshi/ebiten/blob/v2.7.2/ebitenutil/debugprint.go#L48C3-L48C32 trivially replace with:
The text was updated successfully, but these errors were encountered: