Download Axe Parser 0.4.4. I had a crash occuring on that one. Also maybe a contest entry like guy602665.

Tested both of those and both ran fine. Do you have two calculators open when you try to send these files?

Ok now it works with the regular version but not the 64 bit version. Fortunately the regular version works fine so I guess I'll use it for now.

However, now when clikcing the screen it crashes.

Also it still won't let me export apps...

dragging the screen appears to cause it to crash in release, i'll remove spencer's code for now till he finishes.
group sending works in the 64 bit version, as does app exporting? you can't drag anymore you have to use the export button
i tested both, so i might need more specific steps to follow, or possibly the files in question

BUG!
I can only press one key (on the keyboard) (32-bit version on Win7 64-bit) and then pressing keys doesn't work any more, not even clicking on the skin (which I can click on as many times as I want and it will work until I press a key)

Cutout mode? im not sure about this one, might be a windows bug might not. my guess is a focus issue with the layered window basically what happens is it misses the key up message and so its continually sending the key down. since the calc sucks at handling multiple keys it appears unresponsive
EDIT: aha! fixed. my guess that the little buttons were stealing my messages was correct i will post the updated version later today, hopefully when i submit it. i have to finish the rom wizard and see if i can fix the 84pse cutout skin

Does it works pretty well with unsigned apps?

It should, I don't actually mess with the data, just size it up and throw it in the 8xk wrapper file. Keep in mind the testing done on this was pretty minimal, I didn't test it on a real calc (only on wabbit to see that it validated). Also if you send an app then reexport it, it will probably be slightly different then the original size wise. I think this is ok, but not really sure so let me know if issues arise

Also two more bugs off the list. @Deep Thought this includes your sending an app of a different size already on calc

Ok I tried the 64 bit version on Windows 7, I was happy to see emulation speed no longer takes a minute to get updated when you are at 5% then decide to set speed back at 100% using the slider. I was also happy to see it finally supported 1% mode. However I ran into a problem:

-Pressing F7 or selecting variables cause the emu to crash. I get the "Program has stopped working and must close" message.

-Regardless of if screen palette or grayscale is chosen in gif capture options, it will still capture in grayscale anyway.

First should mention that both of these are fixed.
Secondly as i mention in the Pokemon Red thread, I'm working towards a ticalc release, and I'd like to iron out as many bugs as i possibly can. The list of all bugs is here (filter by open wabbitemu issues). If you find or know of a bug not on the list, please report it to me ASAP, either here or IRC are good choices. My goal is to upload by thursday night, but if i find any show stopping bugs that will be pushed later

Big thanks to all those who already dutifully report bugs, remind me and I'll add you to the credits if you would like

When do you hope to have this version of Wabbitemu ready?

In theory by this thursday, since I'm moving saturday. However if I cannot satisfactorily get rid of all the issues then I'll push it back and make the release whenever possible

If you have extra ram pages, you might as well just swap in the ram page and use that to execute the code Also if you need more 8.8k of executable code you should really be using an application. That's really what they were created for and the reason the 8.8k barrier exists.

Quote from: Hot_Dog on August 22, 2010, 08:47:53 pm

Quote from: Builderboy on August 22, 2010, 08:42:21 pm

Im curious as to what happens if you have a second page with only data and no actual code?

You could probably theortically access this data, but if so it's a lot more complicated than meets the eye.  If you try to access it simply by using code from your first page, you could crash your calculator.  It's much easier to load it with your own code on the data page.

that's: ouch. So basically you can't have a game engine on page 0 and game data on page 1. That sucks, leads to alot of duplicate code i guess...or am I misunderstanding?

If its pretty small then yeah you can duplicate it or if its speed critical. Most of the time anything like data is stored on a separate page(s) and then loaded into RAM (this also conveniently encourages you compress your data) since your ram page is visible to any app page.

Also Jerros, I'm going to shamefully plug spasm here, but there is really not a much simpler way to build a multipage app. And since im pretty sure AppDev uses TASM any code you've written is (hopefully) compatible. SPASM is here. Once you've got that download app.inc and put it in the same directory as your project.

#include "ti83plus.inc"
#include "app.inc"
defpage(0, "MyApp")
;for bcallin
_AddHLOne .equ $ - $4000
.dw AddHLOne    ;i think address comes first...
.db 1
;all code on page 0 goes here
 ld hl,0
 bcall(_AddHLOne)
 bcall(_JForceCmdNoChar)
defpage(1)
;oh look an incredibly efficient routine on page 1 :D
AddHLOne:
 ld de,1
 add hl,de     ;lalala
 ret        ;impossible to optimize btw ;)
validate()
And then run

spasm -T -L infile.asm outfile.8xk

in the command prompt (or I recommend creating a .bat file). And boom multipage app. I think the code i wrote will work, but its like 5 am here so yeah i'm starting to crash

I should also mention that if you need some better speed than TIs bcall routine (which require 800-1000 clocks overhead), you can write your own page swap routine. Its not terribly difficult, just load it to ram, and mess with port 6. I might post one later, but I can guarantee whatever I write now won't work

The "wriggle" you guys see in the air is the movement of the char 5 pixels down, so he can reach his destination fast enough. Not sure how much I can do about this. Also another update, I've begun reworking part of the core engine, because unfortunately I wrote it broken (mainly cuz I didnt know any better ). Its working better now, but they're are still a lot of bugs to find and fix so don't expect a release anytime soon