Small suggestion, but could you take off the 2 character cap on labels?

This is all stuff you could do yourself from a program, I believe. It's not worth implementing in Doors CS[E] themselves. I'm afraid I don't see the point of both horizontal and vertical scrolling. That sounds confusing. No.
Cool, I look forward to taking a look at it.

Not easily. I don't think it's worth it, personally. Sorry!

Bug: I used the input command with a variable, and my code was Input("",A. The input displayed a square, my calculator whitescreened, and then it reset. Fix?
Suggestions:
-bumping up brightness
Question:
When will 8.2 be released? (beta if available)
Off-Topic:
Will we be seeing mobileTunes 3 for CSE/CE anytime soon?

While I cant say anything about your bug, I can answer the off-topic suggestion. Partially.

I have no Idea if MobileTunes3 will be launched on the CSE model, but the CE Model has no I/O port. This means that you have to figure out how to get audio from the USB port, which may be beyond what most people would be willing to do, just for listening to music from their calc. Therefore, I sincerely doubt that Kerm would release MobileTunes3 for the CE model.

I would like to see MobileTunes3 ported to the CSE. Also, I own some headphones that have a USB port. If you don't, you could always get an adapter. It's not like most headphones work in the CSE anyway...

I couldn't replicate this with Doors CSE 8.1.2.

Possibly never. It might also be "eventually" (ie, when the TI-84 Plus CE version of Doors CSE is done) with features back-ported from that version.
Given that the new calculator lacks an I/O port, it is unlikely.

Doors CSE supports assembly programs over the $C000 limit, as long as you have enough free RAM for the RAM copy of the program. If you make sure that once the program is copied to (UserRAM), no code is past $C000, Doors CSE can run any program up to the size of your free RAM. However, I unfortunately can't think of a good way to run archived ASM programs larger than the free RAM.

Edit: I should further clarify that I don't want to include any Flash unlock exploits in Doors CSE, so I can't make $C000-$FFFF executable.

Yes, that does make sense. Just will have to find a way to relocate portions of code to different ram areas and execute from there instead. Thanks for your response; I deleted it once I realized that it wouldn't have worked in the first place.

Ah, sorry that I snuck it back into the thread, in that case. If you have more code than can fit below $C000, you unfortunately will indeed have to copy it elsewhere (like $8000/ramCode) to execute it.

In the past it was mentioned that there is a bug in DoorsCSE where the alpha hotkeys do not work after running DoorsCSE.
In the animated screenshot below, I load DoorsCSE and a program into archive.
I then open DoorsCSE and run the program.
I enter a value in by pressing [2nd].
After I input the value and press [Enter], I quit the program by pressing [Clear].
I then press [Enter] as DoorsCSE prompts in the status bar.
I quit DoorsCSE by pressing [Clear].
Finally, I try the alpha hotkeys. None of the hotkeys work.
To fix this, I run DoorsCSE via the [On][Prgm] keyhook and quit with [Clear].

Thank you for your help tracking this down! If I follow your steps exactly, I can replicate the bug.

If I replace the Input with a Disp, the problem does not occur.
If I ClrHome at the end of the program, so Doors CSE does not pause, the problem still occurs.
If I run Doors CSE via the Apps menu instead of the keyhook, it also fixes the problem.

No! We must have an 8.2 release! CALCnet is begging to be here.

My experience with this has only ever been that running a program through Doors CSE disables the hotkeys, and that then to go back inDoors (whether via Apps or ON-PRGM) and then immediately outDoors (via CLEAR) removes it. I assumed that must be well known. Are there any other ways round it?

That seems to be the main way around it. I'm disappointed to hear that this is a widespread problems with programs that use Input/Prompt, though, and I'm trying to track down which flag or hook interactions are responsible for the problem.

Two feature requests:

1) Ability to run a program whose name is in a string.
2) Ability to "register" custom headers with a program, so that a program with that header will be run with the program that is registered. The registering program would have a function to get the name of the program that ran it in a string. This would facilitate custom level sets and such. (I probably would say no to this request unless multiple people wanted it. I know I'm kind of unique in some of my wants )

bump

Also, could we have the ability to disable ERR:BREAK while running BASIC programs in a setting or something? They're running in a frame, so it would be possible.

Is it too complicated to use the Celtic 2 CSE functions to put "prgmNAME" in a program and call that instead? I certainly will be the first to admit that that's not very elegant.
Doors CS 7 tried to provide this for ASM programmers, and I think Document DE (and maybe mobileTunes 3) are the only programs people actually use that exploit this feature. I doubt this will find its way into Doors CSE for ASM or BASIC programmers.

I don't know what you mean by "frame", but they're not running in any such thing. Yes, I could make programs able to catch [ON], but I won't, because it's too easy for newbie TI-BASIC programmers to lock up users' calculators that way.

By frame I meant that BASIC programs are running background tasks and looking for certain key presses and code snippets to be executed via ASM, such as real(7,9,x,x,x,x,x). Could it be an option in the DCSE settings or implemented in Hybrid BASIC functions in the future?

NOOOOOOO! Will it not be released for either calc or just not for the CE? Because I really want this mobiletunes program. If you are not planning to work on it anymore, could I please have what you have done? Thanks so much!

Actually, that reminds me: Kerm, if you wouldn't mind, if you were to send me the source thus far, I would be happy to touch up on things and add a whole slew of GUI things and more features, if desired. Thanks!