Quote from: Xeda112358 on November 14, 2010, 03:35:55 pm

Okay, thanks! I think that I will post any other problems I run into, here.

Why don't you post them in Recode Thread, just asking :s

Good point... Sounds a little more intelligent

Well, the problem isn't there anymore, but I am still curious about what happened and I did actually want curCol and CurRow, but the penCol and penRow might be fun to play with. Any who, here is what ConvRStr does:
This is used in my BASIC ReCode project to convert real number strings into hex
Inputs:
     HL is the pointer to the real string (or the byte before)
Output:
     (86ECh) has the converted value --This will likely change, but for now it is this
     BC contains the converted value
     HL points to the byte after the string
So when I was making the "Disp " command, I would do something like Disp 1,2,HELLO and it would need to convert that 1 and put it in curCol, convert the 2 and store it it curRow, and then display HELLO. Again, it works now and before, the values were converted correctly, but before I actually added the displaying portion, it wasn't setting the cursor where I wanted it.

I am pretty sure it was because after the ReCode section (so in the BASIC part of the program), I used "Pause Ans" to check where the cursor was.

Okay, my latest update now has the Line( command which is used to draw rectangles. I actually made the example program prgmB do something this time and I have the compressed version of the program called prgmRECODE.

At the moment, you can comment on your code without a problem unless you use commands. The problem is, every byte gets read by the interpreter and this can slow down your code. I was thinking about using "." to start a comment and have it skip to the next line to save speed, but if anybody has a better idea for starting a comment, I can easily change it.

Also, the example program has a pause just about every other line, so it isn't slow, it's just taking a pause so you can actually read the words

Finally, this is as far as my original version got. Now I get to be a little more inventive. I am going to take it slow and easy, but if there are any ideas, I would be happy to read them. I do not plan to do anything major like a tile-mapping routine yet, but simpler things are okay.

Well I am going to eliminate OS routines later. For now, I am just making it so that I have an outline, but that might be cool...

In my latest program I am having a problem with this code:
Call ConvRStr        ;Converts a decimal string into hex and stores it to BC
ld a,c
ld (curRow),a
Call ConvRStr
ld a,c
ld (curCol),a
ret
ConvRStr converts a string of decimal digits into hex in BC. So "123" would make BC=7Bh. ConvRStr works properly, but the code isn't setting the cursor position correctly. Any ideas why?


EDIT: Okay, never mind. I have no idea why, but I decided to add the code to actually display text and it worked. I am still confused about why it didn't work before, but it works now. My problem is fixed now.

Oh, well there is a neat twist!. So you are going to be making the routine for how Output( and the like act? That is really nice and that will make the routine fast as well.

yeah, my only goal in the spread sheet was to make it take all of my code and put it all together. It was designed for my uses, but anybody is welcome to use it.
Column A is the name
Column B is the size of the code in bytes
Column C is 1 if it is to be included in the final code, 0 if not
Column D converts Column B to hex
Column E is the start address of the code
Column F is the hex code
Column G is whatever F is if C is 1
Column H is all of the code in column G
Column I is the address as it is used in hex (1234→3412)
Column J is the length of the hex code (uses !!! if it doesn't match B)
Column K is the cumulative size of the code to be used

well, I learned BASIC first, so if you need any help I can try to give the BASIC or English behind assembly I started playing with Celtic 3 and modifying data before I really figured it all out.