-
Notifications
You must be signed in to change notification settings - Fork 9
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
Vectorize coordinates in draw commands? #35
Comments
What about a separate function like Moreover: |
Wait its Screen.line |
not draw.line |
unfortunately until lists get added this will not work :( |
Draw commands often refer to paired x,y values. I've now mostly finished vectorized operations, including the ability to "unpack" vectors into commands like
dst()
,atan2()
andUnit.move_to()
that require x and y as separate operands in a single mlog instruction. Should I use this same machinery for draw commands? This would provide consistency, and also make some mathematical operations involving drawing a bit easier to perform: e.g., the midpoint between points A and B is (A+B)/2. It would however make raw draw commands a tiny bit more cluttered, e.g.draw.line( [0,0], [10,10] )
rather thandraw.line( 0,0,10,10 )
, though arguably these cluttering brackets actually make it more readable.The text was updated successfully, but these errors were encountered: