- When demonstrating something to students on the screen, it would be nice for students to be able to see what keys were pressed to do some task. Wabbitemu has a good visual feedback when pressing a key, but no way for a student to know what was hit
if they weren't looking at that moment. An option to show a list of recent keys pressed would be great, or perhaps even just an optional indicator like a yellow outline of the last key pressed.
Hmm this is a tricky one. Keeping a list of keys is doable, although there is a difference between the keys you press and the input the calculator receives (I'm not sure which one is more important to you). Another possibility is to make it so that you can
specify a period of time for the key highlight to appear for (say 2 seconds of highlighting that key). This has the advantage of working nicely with the existing stuff but isn't as clear as a list. I'll play with a couple things and see how it turns out.
- Make "Enable Skin" the default.
Eh. Spencer and I personally perfer the skinless mode (which is why its like this), and its not hard to change. This along with the option to save your state on exit by default is the two I hear about often. And since it really just comes down to preference
I'm just going to keep it how it is for now, sorry.
- In the ROM Setup Wizard: Most school users are not familiar with running assembly programs. Could you also send a 1 line BASIC wrapper program containing Asm(prgmROM8X) and instruct users to run that one instead. Since there's the option of
auto-sending ROM8X via TI-Connect, would it be possible to auto-receive D84PSE1.8xv and D84PSE2.8xv in the same way? If not, it would be easier to transfer these two files manually if they were both Archived so that they'd both be in the same place in
TI-Connect (not to mention saving ram if users don't know to go back and delete D84PSE2.8xv).
Haha how did I know this was going to come up. I suppose I could write a wrapper program, I was just hoping to avoid it. I rewrote rom8x (it used to require running two programs and different programs depending on the model calcuator you were dumping),
and added my awesome graphic showing how to do it, but I guess you're right, a BASIC program would be best. Also for auto-receiving the appvars I don't think this is possible. I haven't found a nice way to talk to TIConnect so all I do is just load the program
into the sender. I could probably open the program you use to grab the app vars from but thats about it. As for not putting the second var in flash, its because I don't like killing your flash chip. I forget that TI doesn't list them in the same place, I can
- I'm looking forward to the key assignment option working. (My habit of hitting Backspace for editing is hard to break.)
Oh yeah, that. Should probably finish that :P. It actually was working, it just wasn't persistent after you closed wabbit. And then I forgot about it and it broke itself.
Thanks for all your feedback I'll see if I can get your issues fixed and upload a new build sometime tonight.