Hmm? Which hotkey, dragging scrollbars?

Opening DCS from homescreen, it could also be 2nd+Clear, and what would be really cool, would be the ability for DCS asm programs to have a 'pause' button in which the game or whatever would pause, and you could 'minimize' the screen and do other things and return to your game.

Yes, I know, I meant he could add that call into his implementation of idetect.

Brandon is always correct.

How about actually implementing the Mirage libraries? (most of them, anyway)
In particular, I'm thinking of setUpInt. The tasker interrupt is needed to exit some Mirage programs, and you could only enable it for Mirage programs.

1)I agree with Tari. I believe my MOS program uses an interrupt because I can't quit a started game unless I lose and that's rather frustrating.
2)I don't think there needs to be DCS hotkey from the mainscreen. Then again, DCS is [apps] + [4] so I don't really ever SEE the apps menu for more than a blip of a second....
3)[reiteration of last statement] DCS could use a little graphical touchups here and there. The folders IMO could use a little redesign.
4)in shell program editor maybe?

Actually, why should DCS run MOS games? Why not just make DCS only versions of them that are 2x better?

The shell has to get more popular for people to develop for it and it won't get popular if it can't run their MOS games.

Tari & Keith: no offense, but DCS already supports SetUpInt...

oops forgot my "[/joke]"
What about my 2nd, 3rd, and 4th statements?
Touchups don't matter THAT much considering I'm the kind of guy who'd sit and add the Hex code for my own BASIC icon idea at the start of every single basic program on the calculator ^^;

In-shell program editor isn't going to happen for a long time, but I hear you about graphical touchups. What kind of touchups do you mean?

I am too lazy to actually make my own post so instead I quote people and then don't say anything new

That could be an SE only feature, where it copies the RAM to extra pages to save everything.

Edit: Or at least save the SafeRam...

What was the point of the I am too lazy to actually make my own post so instead I quote people and then don't say anything new? I really doubt he's going to edit and lie about that...

Well, honestly, I find that the icons are a bit bland. I think that the TIOS basic and asm icons need to be a bit more graphic and a bit less text. Also, the folder icons IMO look kinda...wierd...to me. The angle they're drawn at bugs me every now and then.

It was so you'd know what I was talking about. And I am too lazy to actually make my own post so instead I quote people and then don't say anything new means "Quoted For Truth".

Ah; last I had heard (an extremely old post), setUpInt was not implemented. You should probably finish most of the Mirage libraries if you haven't yet, though.

I think it supports the call, just doesn't use the tasker interrupt like MOS does.

Exactly. I see why you quoted it, but it wasn't for truth. You I am too lazy to actually make my own post so instead I quote people and then don't say anything new so the person can't edit their post some other time. It stops the person from flip-flopping on issues.


...but urbandictionary.com has both meanings, so we'll let it go.

But then, if it doesn't run the tasker interrupt, how can you say it's implemented? You can hardly say it's Mirage compatible if routines don't result in what a program will expect it to do.

Tari, no, here's the difference. It only enables the tasker if the program calls SetUpInt. Do you want me to have it automatically enable the tasker for all MOS programs?

OK, I thought there was no support at all for the tasker, as I had seen no indication otherwise. Thank you.
Are there any Mirage entry points other than runProg which haven't been implemented?