Repository navigation
Replies: 2 comments 9 replies
|
All of the variable names are from information derived from inspection of the Processing Jar file. For https://processing.org/reference/rect_.html I do agree that a, b, c, etc is not that helpful. It might be possible to add a variable name override to the metaprogramming code. Someone would have to dream up new names for variables though. Starting with |
4 replies
|
No urgency here, I just wanted to comment that it dawned on me that, before being used for type hints, Python's function annotations were just, you know, annotations! There are some, a bit clumsy, ways of doing both at the same time, like: https://peps.python.org/pep-0593/ |
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Using Thonny one can get docstring information and some tips about the arguments when calling a function/method.
For size() this is brilliant (width, height; width, height, renderer; width, height, renderer, path)
But for rect() not so much (a, b, c, d...) and I know that rect modes make the positional arguments meanings vary a lot, but, is there something we could do to improve these hints?
All reactions