Decided But definitely a try. Apps would have to be somehow editted in portions since their so large though.

Uh-oh. people hacking DCS on calc...

Nada, would have to have a de-compiler. And beside, I already have the DCS5 source. If I edit anything, it'll be the images for the stack items (i told Kerm they need to look better)

Like a theme change for ya PC.

Heh, but how would you find the locations of the theme items as they shift around between different versions? Either way, I look forward to seeing assembling in action.

Well, it wouldn't be too hard...Just tell a program to look for the hex code of each image in the flash.

Anyway, here's an idea as to how I'll extract parameters from each line of code...

1.)Different parameters are separated with spaces, commas, and parenthesis
2.)The first parameter is always copied to a command buffer
3.)If it starts with a letter and has less than 3 chars, add it to the command buffer.
3.)If it starts with a letter or underscore and has more than 2 chars, equate the value of a label, store it to tempword and add a * to the command buffer.
3.)If it starts with a ",',%,$,@,#, or a number equate value, store it to tempword, and add a * to command buffer.
4.)Look up the command buffer in program memory and copy its value to the program memory.
5.)If the command buffer includes a *, copy 1 byte from tempword to the program, if 2 *'s, copy 2 bytes from tempword to the program mem.

Restrictions are that all labels must have at least 3 chars and all sections for table commands (except the first word in the command) must have less than 3 chars.

Any thoughts?

Anak, what about if it's a number, like ld hl,45202d or add b,4Fh or ld de,(0x9D95)?

again, when it checks for commands and labels it checks for letters, if it comes across a number, %,$,#,or a @ is knows its a numbers.Do you think less than 3 chars is sufficient for a command param?

Oh, and I like the setup for the last one, 0x9D95h though I would edit it to use for custom base numbers like, 2x0010100 (bin) 8x80 (oct) 16x9D95 (hex) or 7x345 (hect or base7)

Well, there's hl/bc/de/ix/iy, ixh and ixl and such. I can't think of any registers that are more than 3 chars.

Aww, you won't let people pick arbitrary formats?

just thought I'd make good use of my GetBase routine... But ok.


Crap! I forgot about ixh, ixl, iyh, and iyl! I guess I'll either have to have it check for labels over 3 chars, or any label less than 3 chars will have to start with an underscore.

That makes sense then, go for it. That will help keep your program's size down, so that's always a good thing.

ixh, ixl, iyh, and iyl are also called hx, lx, hy, and ly, so that all registers are either one or two characters in length.

Really? I've never heard them called that before.

Me neither...hence the reason the command paremeters are 3 chars or less, and labels can be less than 3 chars, but will have to start with an underscore.

The coolest thing is that my assembler uses the #def statements and the \ multiple command symbol so you can make functions like:


Code:


This saves a lot of space in some programs.I'm trying to decide right now whether or not I should add the .module since my compiler's case insensitive.

By the way, did you test out ProgPad with the new vectors in Doors CS 6.6 beta? Be aware the my versions are different from yours and use a slightly different data format; check out the wiki for details.

Nah, I check it though. SirCmpwn just got me hooked on Blender and I've been drooling for the last few mins.

Kerm, good news! The reformatted my stack items and the routines you added are 100% compatible! However, I'm still facing issues with the saving part. Here's the source, see if you can find the err:


Code:

Can you describe the mode of failure with saving, or should I just compile it myself and take a look?

You can get a better idea compiling for yourself, but basically, the screen just turns white and the calc shuts off.Turn it on and a RAM clear.I uses a TI-83+ rom on WabbitEmu. By the way, I added the checkered starting screen that DocDE uses.

Ah, and indeed I was able to replicate your problems when I compiled and tested it. I see that the crash happens after I enter a name and hit save, you must not be passing the proper arguments in or something? I'll edit this post if and when I figure it out,.

I just updated the source above after you compiled but anyway, I use the same method to get the size and data when I open files as I do to save them.If you make a DocDE file you'll notice the FileOpen routine works.

Try ProgPad now!