How to use Arrays Using Pic Basic Pro(need help)

[MrSafe]

Yes I am 100% sure I am using PIC Basic Pro.

Im not sure why arrays wont work for me everything else I can manage but I would love to use arrays, can you point me in the direction or give me a example of how to use an array where if the user pushs a button on the keypad and it stores it in the element and then it increments to next element?

I know of other methods of storing the values inputed by the user but it would require a VERY lengthy code.

I will try and upload my current code but but please be nice :P I am still working on it as soon as i figure out the array problem it will cut my program in by 2/3.

[Darrel Taylor]

Ok, let's see what we can do.

First off, the brackets.
Use square brackets when declaring the Array, and round brackets when using it.

That's not always a requirement, but if you are using statements like SEROUT that uses square brackets, PBP gets confused with the square brackets inside other square brackets.

And, the SEROUT syntax is different than shown ...

Include modedefs.bas

temp  VAR BYTE[48]

SEROUT PORTD.0, T1200,[temp(x)]

Also note that you are recieving/sending BYTEs, not WORDs. So the array should be BYTE[48].

will try and upload my current code

Great, that'll help, cause I'm still trying to figure out what you were trying to do with the temp array.

but please be nice :P

I promise that even if I'm mean, I'll do it in a Nice way.
<br>

[MrSafe]

What im trying to attempt is when the user decides to input a message I would like to store every keystroke in the array until he or she is satisfied with the message then I would like to send the message by using arrays I can easily loop the message so for example the user inputs "Accident near exit 101" . I would like to store that in an array and since I will be storing every keystroke the program will take "A" and store it in temp[0] then store "c" in the next array element which would be temp[1] and so on.

Also I went and uploaded my current program to clarify that I am using PBP

[Darrel Taylor]

Yup, that's PicBasic Pro.

First thing to do is to change the keypad routines so that it only "gets the key's".
This will also reduce the program size quite a bit. Sending to the LCD and SEROUT can be done later, once you know what the character is.

There are other ways to do it, but I'm trying to keep it in the same context as your program.

For instance, with the alpha1: routine.
It can be reduced to ....

alpha1:
    gosub getkey
    LOOKUP key,[" ABCDEFGHIJ"],Char
RETURN

Same for the alpha2 and main getkey routines.

The idea is that the actual character you want will be stored in the "Char" (byte sized) variable. Then you can do what you want with it later, instead of 36 different versions of what to do with it if a certain key is pressed.

Then, once you have the kaypad routine only returning the desired characters, you can do something like this...

Finished VAR BIT  : Finished = 0
StrLen   VAR BYTE : StrLen = 0

while not Finished
    gosub getkey
    if Char != EOM then ' End of message key
        htxt(StrLen) = Char
        LCDOUT Char
        StrLen = StrLen + 1
    else   ; originaly post as an endif (DOH!)
        Finished = 1
    endif
wend
SEROUT2  PORTD.0, 813, [STR htxt\StrLen,13,10]

Of course, this doesn't allow backspaces and the like while editing. But I gotta leave something for you to do.

HTH,

[MrSafe]

The backspacing and what not are very easy for me to figure out in fact I have several methods my main concern is arrays and to understand them I have been reading on what you said earlier about using byte size and honestly when I read that after you told me I almost punched myself in the gut because my brain immediately was like "oh yea...."


The Keypad routine currently just gets the keys it does nothing else I myself display it on the lcd.

******
gosub getkey
LOOKUP key,["ABCDEFGHIJ"],Char

how does this work I have seen this before but I could never wrap my hands around it and get the feel for it.

*******
Finished VAR BIT : Finished = 0 ;;I'm a little confused here are you commenting it or is it part of the declaration?( : Finished = 0 )


StrLen VAR BYTE : StrLen = 0 ;; Same thing is it just being commented on?( : StrLen = 0 )

while not Finished ;; is not part of PBP? in my book it does not even suggest anything of this nature


gosub getkey ;;Understand this portion

if Char != EOM then ' End of message key ;;is char the key that is received from the keypad?

htxt(StrLen) = Char ;;I understand this portion just need to know what Char is

LCDOUT Char

StrLen = StrLen + 1 ;;Does this increment to next position?
endif
Finished = 1
endif
wend
SEROUT2 PORTD.0, 813, [STR htxt\StrLen,13,10] ;; May I still use SEROUT or Must I use SEROUT2. ( [STR htxt\StrLen,13,10] I do not full Understand this portion could you explain to me what this is doing?) Also why do you have 2 endif statements?

Forgive me for my ignorance I have been writing assembly for about 2 years now and I heard PBP was the next step and its been fun just a couple of walls I have to climb over frankly biggest wall is this array problem! I never had to deal with arrays before.

Thank You Soo Much for taking the time and effort to help me I understand you have much better things to attend to and I appreciate all that your willing to do to help me!

[Darrel Taylor]

while not Finished ;; is not part of PBP? in my book it does not even suggest anything of this nature

Really?
You must have a very old version.
While:Wend has been there for as long as I can remember.

In case it's just an old manual mixup ...
Try looking here.
http://www.melabs.com/resources/index.htm#Manuals

LOOKUP key,[" ABCDEFGHIJ"],Char

how does this work I have seen this before but I could never wrap my hands around it and get the feel for it.

There needs to be a space before the "A", just because your keypad routine only returns values starting at 1, and Lookup starts at 0.

LOOKUP is pretty straight forward.
It returns the value from the "List" of items that corresponds to the "key" value.

If key = 1 then after the statement, Char will be "A". And ...
key = 2, char = "B"
key = 3, char = "C"
etc. etc.

Finished VAR BIT : Finished = 0 ;;I'm a little confused here are you commenting it or is it part of the declaration?( : Finished = 0 )

Ummm, we'll call that the "skimask initialization syntax".
You might get that later. Inside Joke.

But no, it's not commented. The colon ":", separates two statements, as if they were on separate lines. I.E...

Finished VAR BIT : Finished = 0

; is the same as

Finished VAR BIT
Finished = 0

StrLen = StrLen + 1 ;;Does this increment to next position?

Yes it does.

I know there's more questions, but let's see where this get's you?
<br>

[SteveB]

Ummm, we'll call that the "skimask initialization syntax".
You might get that later. Inside Joke.

But no, it's not commented. The colon ":", separates two statements, as if they were on separate lines.

Standard BASIC syntax from "In the beginning...."

Anybody remember Beagle Bros. Two-Liners? What could you do with 2 lines of code, packed as tightly as possible? I think it was 64 characters max per line, but can't remember.

I have actually picked up the technique again, for the same reason Skimask mentioned: Less scrolling, more compact code listings, keeps related code elements together. Once I got used to it again, I found it easier to read (as long as it wasn't used excessively). Thanks Skimask!

SteveB

Edit: A little research yields "less than approximately 150 characters" per line of Apple II code. Page 23 (26th pdf page) of this reproduction 1978 Apple II reference Manual

[MrSafe]

Really?
You must have a very old version.
While:Wend has been there for as long as I can remember.

In case it's just an old manual mixup ...
Try looking here.
http://www.melabs.com/resources/index.htm#Manuals

There needs to be a space before the "A", just because your keypad routine only returns values starting at 1, and Lookup starts at 0.

LOOKUP is pretty straight forward.
It returns the value from the "List" of items that corresponds to the "key" value.

If key = 1 then after the statement, Char will be "A". And ...
key = 2, char = "B"
key = 3, char = "C"
etc. etc.


Ummm, we'll call that the "skimask initialization syntax".
You might get that later. Inside Joke.

But no, it's not commented. The colon ":", separates two statements, as if they were on separate lines. I.E...

Finished VAR BIT : Finished = 0

; is the same as

Finished VAR BIT
Finished = 0

Yes it does.

I know there's more questions, but let's see where this get's you?
<br>

Thank You I will go and test this out I will be gone for a few days but I will return with the result. Thank You again

I know understand a little bit im still confused on how to use arrays specifically but this portion I understand to a great degree.

I understand how to declare my array but thats about it however I will tr first with this knowledge and see if that works. I hope this thread isnt closed :-) If you dont mind I will beback with a few more questions thank you again.