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
The Surface class has many getters and setters. Some of them are very commonly used and I feel that their verbosity can be cumbersome.
I'm thinking of
.get_size()
.get_width()
.get_height()
I think it would quite elegant to be able to do
.size
.width
.height
These would be read-only properties, I don't think it makes sense to try implement scaling when these are changed.
Why am I thinking of these and not other getters/setters? These are the good starting ones in my opinion, because they're common and seem pretty unambiguous.
What do other people think?
The text was updated successfully, but these errors were encountered:
The
Surface
class has many getters and setters. Some of them are very commonly used and I feel that their verbosity can be cumbersome.I'm thinking of
I think it would quite elegant to be able to do
These would be read-only properties, I don't think it makes sense to try implement scaling when these are changed.
Why am I thinking of these and not other getters/setters? These are the good starting ones in my opinion, because they're common and seem pretty unambiguous.
What do other people think?
The text was updated successfully, but these errors were encountered: