This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - thepenguin77
Pages: 1 ... 29 30 [31] 32 33 ... 108
451
« on: December 03, 2011, 11:15:20 pm »
Will the new update also include grammer hooks?
Maybe, probably not yet What about ON + MATH? It wouldn't replace anything and doesn't seem to be in use.
I was thinking ON + MATH, but that's a little random. It does fit my needs though. Yeah, that wold be great.
And I have another feature suggestion: A menu point to deactivate the On+Vars hook!
I have to assume you mean the abort button and I can't do that. The abort occurs before the appvar is located and therefore I would have no way to determine if I should abort or not. Also, I can't do it after I check the appvar because if the appvar is corrupted, it will crash when it tries to determine what to do. Then you'll have to reinstall your OS... But, the real reason that I am posting is because I am putting together an API for zStart. Currently I only have two entry points: runOP1 and editOP1. What else does zStart do that you would want to do with an assembly program? (perhaps on ram clear or turning on for instance)
452
« on: December 03, 2011, 10:49:25 pm »
Ok, a slight change to my code:
ld hl, offsetToError
ld (errOffset), hl
ld a, 3
ld (menuCurrent), a
ld a, 1
ld ($85DF), a
ld a, kEnter
bcall(_pullDownChk)
bcall(_clrTR)
ld hl, op1
ld de, progToEdit-1
ld bc, 9
ldir
ld b, a
ld a, kError
ld (cxCurApp), a
ld a, b
bcall(_newContext0)
bcall(_mon)
The previous one didn't quite do the Goto properly, so this version starts off acting like the edit menu, then switches gears and says it's the error menu doing a goto. In any case, (errOffset) is how far it will jump.
453
« on: December 03, 2011, 03:38:34 pm »
A little disassembling and this is what I came up with:
ld hl, offsetToError
ld (errOffset), hl
ld hl, op1
ld de, progCurrent-1
ld bc, 9
ldir
ld a, 3
ld (menuCurrent), a
ld a, 1
ld ($85DF), a
ld a, kEnter
bcall(_pullDownChk)
bcall(_clrTR)
bcall(_newContext0)
bcall(_gotoErr)
bcall(_mon)
This method essentially fakes a person going into the program menu and editing a program. You can leave out the bcall(_gotoError) if you aren't going to initialize (errOffset), but then it won't scroll.
I believe this will work from an app, but I've only tested it from a keyhook so far.
454
« on: December 02, 2011, 08:44:47 pm »
Ztrumpet brought up the point that it would be useful if instead of refusing to jump to an archived program's error, it uses zStart to bring up the editor instead.
The offset to jump to when the error occurs is stored at an OS address correct? If that is the case, then I can add an api entry point to edit a program and you can call it if the error occurred in the archive. Since I end up opening a program editor anyways, the goto function should work like normal.
If you want to do this, I'll also have to know how you are opening the program editor. (I've never looked very far into it)
Edit:
That was easy
455
« on: December 02, 2011, 08:38:43 pm »
It's probably possible, I've been meaning to add some api entry points for a while now. I'll see what quigibo says.
456
« on: December 02, 2011, 07:53:17 pm »
Nothing, ON + + is base conversion at the homescreen, but it's undefined in the program editor.
457
« on: December 02, 2011, 07:36:39 pm »
I'm working on the next update, which means reading back through all the pages since the last update, but I've reached a problem. I added keyhooks to run MirageOS and DCS, but the DCS hook uses Prgm, this means that my Copy function can't use Prgm as well.
So, now that 2nd, Mode, Del, Alpha, Stat, Apps, Prgm, Vars, Clear, ^, and Enter are all taken, what should I assign Copy too? (I can't capture 2nd/Alpha, Mode is used by Omnicalc, and Clear is well, duh)
Btw, if no one provides a better response, it will be +. (Though + replaces a character if the hook is not active, something to think about)
458
« on: December 01, 2011, 09:04:53 pm »
That has got to be a TAS. But even for that, it's amazing 
It's not a TAS, this guy is good. He once sent me an email where he wrote out the format for a level with notepad showing me the mistakes I had made in replicating it. I believe he plays this game a lot. He's beaten the long haul like 10 times. Not only that, but I would assume that he doesn't even know about the TAS capabilities of wabbitemu.
459
« on: December 01, 2011, 04:31:51 pm »
This is now over on ticalc.org. So, to get the most recent version, you have to download it over there  And you know what, I think I'll put this in the Omni archives as well, I need to start doing that.
460
« on: December 01, 2011, 04:07:03 pm »
That's incredible.
The penguin, before this, were you even sure the level was beatable?
Yes, I've beaten it in parts, just not all at once.
461
« on: November 30, 2011, 11:47:33 pm »
Some guy, (Brandon Wong), who loves this game just emailed me this screenshot. I'm not really sure what to say considering I sent him the game last Friday night.
In any case, here is the full level.
462
« on: November 30, 2011, 05:24:27 pm »
Oh, I changed the syntax on you. Now it's just Fcdf() at the start of the program. I should properly release this sometime...
It's still Fcdf(0) to close it, then?
No, you don't close it, it closes automatically. Just put Fcdf() at the start. Then, imagine that there is a bracket after it that encapsulates your entire program.
I mean, what more do I need to say?
463
« on: November 29, 2011, 02:50:46 pm »
Well, the screenshot isn't a good example because I had wabbitemu set for 12 shades of gray. So when you try to distribute that over 8, 7, or 5 colors, you run into problems.
And yes, it's only for 15MHz models because I used the crystal timers to make the grayscale perfect.
464
« on: November 28, 2011, 05:54:19 pm »
This is a question people ask a lot, will x-level grayscale look good? or will it flicker? Well, now you can decide for yourself. I spent all day not doing my thanksgiving break homework and instead working on this program. It displays all levels of grayscale from 1-8 so you can see what looks good and what doesn't. Controls: - Left / right - swap levels
- / / * - adjust lcd frequency
- + / - - adjust contrast
- 2nd - report lcd frequency
- Clear - quit
Send this to your real calculator and tell me what you think. This can serve as your model for what is possible because I believe I did this the best that I could. Also, if you need some grayscale routines, I'm including the source. Just be warned the 7-level one is a piece of crap. Edit: j/k on the messed up, it was good from the start
465
« on: November 28, 2011, 11:18:29 am »
That's for BIT n,reg8 at least, but my sources say BIT n,(HL/IX/IY) behave differently; BIT n,(IX+d) takes 5 and 3 from (IX+d)>>8 and BIT n,(HL) from .. weird places. Are those sources incorrect?
There are many different models of Z80, so I wouldn't be surprised if there are differences in undocumented flags. Also, I would recommend staying away from IX and IY instructions if you want the programs to work on the Nspire with 84+ keypad.
Actually, IX and IY work fine, it's only their undocumented half registers that don't. For instance, LD IX, $1337 works while, LD IXH, $13 \ LD IXL, $37 does not. To see what instructions won't works, look here. Any instruction in red won't work, (remember though that some gray instructions are duplicates of real instructions)
Pages: 1 ... 29 30 [31] 32 33 ... 108
|
Show Posts