Open ColinTimBarndt opened 2 weeks ago
It would be nice to have a second opinion on this. Should we keep track of the cursor or just accept resetting the position?
Interesting. It might make sense to see how other implementations in other languages like C handle this in their libraries?
I actually haven't looked at other implementations until now. It appears that the status includes the current DDRAM address. I would combine this PR with adding status fetching in that case, which would eliminate two problems at once.
Though, this would first require implementing reading from the bus, which should be a separate PR.
This pull request allows defining custom characters. Closes #8.
This branch is currently based on #54 just for convenience, but I can rebase it onto the current version as it doesn't touch anything changed in that PR.
The current implementation has the drawback that it will reset the cursor position. This is required to change the writing mode from CHRAM back to DDRAM and we are currently not keeping track of the cursor position.
It would be nice to have a second opinion on this. Should we keep track of the cursor or just accept resetting the position?