- I can confirm the problems with key input with both CMonster and Calcuzap when run under Doors CSE. My only theories involve interrupts at this point, but I'm working on looking at the source of the two games (thanks for open-sourcing them, Patrick!) and trying to figure out what's happening.
- Hayleia: I'm impressed that you managed to find that bug; it's quite specific. I can replicate it: Move the selector to the second icon on the last row, wait for the InfoPop popup, then press [Y=], [CLEAR], or [ALPHA]. The brightness will decrement before the requested menu or action is shown/performed. I also have no idea where this one is coming from; presumably some strange issue with the LCD and LCD cursor positioning?
- Merthsoft: I don't think so, because Doors CSE now sets the OS speed before running TI-OS programs. I will soon fix the fact that you didn't get Beta 2.
- The Asm84CPrgm issue: hmm, it didn't occur to me to test that bit. I will soon fix that oversight.
-This one is not a bug, it is just not so natural. When browsing the icons (if you know what I am talking about) when I have exactly 16 programs, going "too high" loops, going too far on the left/right sort of loops, but going too low doesn't loop at all, it brings the cursor to the bottom right corner. I guess it is because it tried to go to the next row even though there is no next row, but then why does getting too high loop ? The intent is that normally, pressing [down] on the second-to-last row when the last icon is below and to the left of the current icon will bring you to the last icon. In diagrammatic form, the cursor will go from any of three As to B when you press [down]: Code:
Here, because B is the end of the current line, it ends up looking like: Code:
# # # #
# # # #
# A A A
I could add an exception when (TotalProgs)%4 == 0; do you think that would be much more natural, or unnecessary?
A A A B
Out of curiosity, does Doors CS load programs directly from the archive or does it put it into RAM first? It copies them from Archive to RAM rather than unarchiving them. If a program does not change contents during execution, it then just deletes the RAM copy. If it changed, it deletes the Archive copy and re-Archives the RAM copy.