Skip to content

Conversation

komoto48g
Copy link
Contributor

Fixes #2748

This PR modifies "wx/lib/floatcanvas/FCObjects.py" and is part of #2448, which currently has conflicts.

@swt2c swt2c merged commit 73ff2a8 into wxWidgets:master May 6, 2025
12 checks passed
@komoto48g
Copy link
Contributor Author

Sorry, I hadn't checked the bitmap drawing test. I've confirmed that the bitmap position is also incorrect.
But I just pushed one more commit—could you revert or reopen this? Sorry for the inconvenience.

@swt2c
Copy link
Collaborator

swt2c commented May 6, 2025

Can't - you'll have to open a new PR.

@komoto48g
Copy link
Contributor Author

Ok, I will!

@urishab
Copy link

urishab commented May 6, 2025

I’m not sure this fix is gonna cut it.
The // operator no longer converts to int.
it just gives the floor of the number but can return float.
so I think you’re going to have to explicitly convert to int to satisfy all cases.

@komoto48g
Copy link
Contributor Author

I can see that, but it doesn't cover all cases. I also tested the Allow and AllowLine cases and confirmed that they have issues as well. The issue comes from passing a float value to dc.DrawXXX.
I will check some more and submit a PR later and would appreciate it if you could review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FLoatCanvas Bitmap & Text always get drawn at (0,0) under Python 3.11

3 participants