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

[python] Implement draw_line, fill_rect in kandinsky #746

wants to merge 8 commits into
base: master


None yet
1 participant
Copy link

boricj commented Oct 25, 2018

These functions are already directly provided by kandinsky, might as well expose them to Python. Still a far cry from what we can do (#416), but these functions are essentially free to implement.

@boricj boricj force-pushed the boricj:python_kandinsky_moar branch from 47daf0e to 8c7daec Oct 26, 2018

@LeaNumworks LeaNumworks force-pushed the numworks:master branch from 2f31f04 to f30df04 Nov 23, 2018

@boricj boricj force-pushed the boricj:python_kandinsky_moar branch from 8c7daec to 31fe579 Feb 2, 2019

@boricj boricj force-pushed the boricj:python_kandinsky_moar branch from 31fe579 to 452d9e1 Feb 2, 2019


This comment has been minimized.

Copy link
Contributor Author

boricj commented Feb 2, 2019

I've added blitting and key reading functions, so one can make "real" games on the calculator now (proof:

Drawing performance is disappointing, probably because the framebuffer isn't memory-mapped, but it's usable as long as one doesn't attempt to redraw the entire screen in real time. The only way to achieve good drawing performance would be to "race" the beam by redrawing the entire screen in one go (like GESTE did), but that would be quite the challenge to do it quickly enough from within MicroPython...

I've moved the Python interrupt key to the Home button. Not sure if that's a welcome change, but two main buttons is better than one and it's less likely someone would exit out of a Python script while trying to hit the OK key.

@boricj boricj force-pushed the boricj:python_kandinsky_moar branch from 452d9e1 to c81ecd1 Feb 3, 2019

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