You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree. I had something kind of working, but it wasn't what I wanted. Setting a bouncing rect is exactly that...a rectangle. So a triangle shape has a clickable area that of a rectangle. That is a bit of an issue there, but that might just be a limitation.
Further when you start changing angles, the rectangle angle doesn't adjust. So you have to import cos and sin to find a bounding rect. We would really want something like this: https://www.mathopenref.com/coordbounds.html where explicit coordinates are given relative to the center point. I will do some more digging on this one.
As pointed out by Avery on the Google Groups feedback thread, devices are clipped improperly when the playfield window is not active.
I believe the following code to be at fault:
➔ playfield.py
The text was updated successfully, but these errors were encountered: