Once capture starts, wait at least 15 minutes before taking any action on the emulated calculator. People will be very happy to wait until the program you wanted to show is ran. Plus nobody cares about dial-up users anymore, anyway.

Also, people usually don't mind waiting an additional 5 minute if you mess up several times when trying to select commands in the CATALOG or programs in the PRGM menu, so don't worry about this too much either. People will be fine.

yes. every single byte must be shown. there are two approaches to this
1) pause at 7 lines. i'm sure the reader will be able to decipher your code that quickly.
2) scroll as quickly as possible, making it as non-readable as possible. if you choose this option, it's suggested you scroll through the program multiple times unnecessarily.

Also, randomly simulate pulling a battery just to prove that all programs get RAM Clears.

That is great Really makes me want to play that game!

EDIT: Shouldn't this be in Randomness? Somehow, I don't think the conversation here is exactly serious, if you know what I mean

Also, randomly simulate pulling a battery just to prove that all programs get RAM Clears.

Is there a way to do that? I've tried, but no emulator allows this Is there a program to simulate battery pulling?

yes. every single byte must be shown. there are two approaches to this
1) pause at 7 lines. i'm sure the reader will be able to decipher your code that quickly.
2) scroll as quickly as possible, making it as non-readable as possible. if you choose this option, it's suggested you scroll through the program multiple times unnecessarily.

Unless, of course, you don't want your source to be viewable. In that case (assuming you're screenshotting an ASM program) unlock the program and start showing all the garbage tokens

Yeah, that would work for most purposes, but I had a problem a few weeks ago where I tried to load a 3^rd-party OS into, say, TI-Smartview (I know, it's definitely not the best emulator, but it's the only one I've found so far that allows loading .8xu files), but I couldn't find a way to do the battery trick to prevent the validation check.

Link please?

I actually nearly did that once. I left WabbitEmu in Record mode for a few minutes, then started to take the screenshot. But then I realized that it had already been recording for a while.

I like how the new WabbitEmu shows a dynamic blue border around the screen when it's recording. It becomes helpful in situations like this

Maybe we could make an entire list of "Screenshotting Guidelines" like "2^6 Ways to Get Your Files Accepted to ticalc.org"?
Unfortunately, 2^1 (or 2^1+1 or 2^2, I don't know how many we're at) doesn't make a good list.
More guidelines!