topic Re: String Arrays in Libraries & objects

String Arrays

Anonymous — Sat, 31 Mar 2007 01:12:28 GMT

I have programmed some objects in previous versions of AC and didn't have this problem before.

I wanted to create an array that a user could use to input some 3 character variables.

If I dimension the variable (I.e., DIM wlunit [10][10] or even DIM wlunit [][] in the Master Script, the user cannot enter any values. In the past, I was able to initialize the array in the Master script and then the user would be allowed to change the values. Now I cannot initialize the array or dimension it.

A part created in AC9 (or was it AC8 that was then saved in AC9) with an array. It has an initialized array and I can change the parameters later in the object setting dialog box.

Is there a correct way to do it? It would be nice to be able to initialize my array.

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 04:47:40 GMT

Phill,
This may be way off base but, have you declared
the array once in the parameter list and then
the same array again in the master script ?
David Nicholson-Cole discovered that this
worked in versions prior to AC 8.0 but
did not work from 8.0 onward.
You declare and initialize the array once
in the parameter list and the user can change the values.

Sorry if this has nothing to do with your issue.
Peter Devlin

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 05:28:41 GMT

Peter,
Thanks for the suggestion. I think you did help me on one thing because I thought about using a dynamic array (correct term?) with an unspecified size but then the array didn't show up in the parameter list and therefore there wasn't any way for the user to enter any information. I added the array in the parameter list and then discovered I had to eliminate the DIM statement.

If I declare the array in the parameter list, how do I initialize the array? I will try a few things.

I may post something to gdl-talk if I can find the link.

Thanks again

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 16:09:09 GMT

You can assign values to the array with the PARAMETERS statement.

I often use a FOR loop such as:

FOR i = 1 TO whatever
PARAMETERS array_1 = something
NEXT i

Naturally you have to enclose this in some conditional statement (with GLOB_MODPAR_NAME or such) or it will constantly override any user input.

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 18:06:00 GMT

Matthew,

Thanks for the hint. I have never used the GLOBAL_MODPAR_NAME in the past except to tinker but I understand the concept and will try that.

Thanks.

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 19:21:37 GMT

Phil,
The way you initialize a parameter list array is the following.
Select the variable type in the usual way (length, pen, text, etc).
Push the array icon button and the array opens but it is a one
dimensional array with one row and one column.
To get more than one row select the row number
which is initially 1 and then push the "insert" button
at the bottom of the dialog as many time as needed.
To get more columns, select the first column number and
press the "insert" button and more columns will be created.
After you have opened the array dialog for the first time
the only way you can open it again is to use the "Set" button
which comes available if you click on the parameter.
After you have set up your rows and columns you
can initialize the values you want.
Peter Devlin

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 19:48:50 GMT

Thanks for responding Peter.

I had created the array as you described but perhaps I am not making myself clear. Assuming I have created a 10x10 array in the parameters list and want to initialize all of the values to "" (null) inside the GDL object.

If I use a FOR/NEXT loop to initialize the array, the user is not able to change the values in the object properties dialog box. I guess I need to use the GLOB_MODPAR_NAME in a conditional statement? I didn't have to do this in the past but...

Regards
Phil

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 20:07:57 GMT

Phil,
I was just playing around with the array parameter
and after the rows and columns are created all
of the values are "null" or blank by default.
As far as I can tell this does not change until
you or the user fills in the cells with characters.
I will check again.
Thanks,
Peter Devlin

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 20:20:08 GMT

I agree that the array gets created as nulls but in the process of testing my part, values get put into the array. I was hoping I could use a FOR/NEXT loop to empty them out but still have the user input their values later.

As I said it worked in previous versions of AC and doesn't now so I just want to know if there is a way to do it properly.

Phil

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 20:28:10 GMT

Phil,
I just checked again and indeed all the cells created
when I make the rows and columns I want are blank by default.
I saved the object, inserted an instance in the plan, selected it,
opened the settings dialog, and opened the array parameter
dialog and all the cells were blank.
I inserted some characters in a few of the blank cells, hit OK
and returned to the plan. I selected the object again
and opened it's setting dialog and checked to see
if the changes I made had held. They did.
I am sorry. I am clearly missing something.
Thanks,
Peter Devlin

Re: String Arrays

Anonymous — Sat, 31 Mar 2007 20:32:15 GMT

Phil,
I just read your last post.
I think I now know what your getting at.
You want to have some sort of "re-set" function.
We will have to think about that one.
Peter Devlin

Re: String Arrays

LiHigh — Sun, 01 Apr 2007 04:44:11 GMT

Phil,
I think that a bigger picture of what you are trying to achieve with your object will help us understand your problem better.

Re: String Arrays

Anonymous — Mon, 02 Apr 2007 22:26:18 GMT

pfeinberg wrote:
I agree that the array gets created as nulls but in the process of testing my part, values get put into the array. I was hoping I could use a FOR/NEXT loop to empty them out but still have the user input their values later.

As I said it worked in previous versions of AC and doesn't now so I just want to know if there is a way to do it properly.

Phil

If all you want to do is reset the values to defaults after editing, just run the FOR/NEXT loop and then comment the code before saving. You can also use this to create initial non-zero values. In fact, I find this easier than entering the values manually in the parameters list (seriously bad interface IMHO).

The user can always reset all the parameters to defaults by switching to another part and back, so all the IF/THEN and GLOB_MODPAR_NAME tricks are only needed for a partial reset or to reinitialize for changed conditions.

Re: String Arrays

LiHigh — Tue, 03 Apr 2007 03:49:27 GMT

Reset is very easy to implement.

create a parameter says "reset_all".

!-----------------script--------------------

IF reset_all THEN

FOR i=1 TO VARDIM1(array)
FOR j=1 TO VARDIM2(array)
PARAMETERS array="Whatever Values"
NEXT i
NEXT j
PARAMETERS reset_all=0

ENDIF
!------------------------------------------

Hope this help!

Re: String Arrays

Anonymous — Tue, 10 Apr 2007 08:42:08 GMT

If you want to create an initiallization part do the following.
Create a variable named for example trigger.

In the master script have a simple code line such as (not gdl code but metacode)

If (trigger = true ) then trigger=false
Else trigger=true

That way you trigger the GLOB_MODPAR_NAME to be set to trigger

then using the GLOB_MODPAR_NAME in the parameters section you can create a code to handle when the trigger parameter changes. Put there all the initialisation code. Simple as that.

Re: String Arrays

Anonymous — Tue, 10 Apr 2007 14:20:51 GMT

oreopoulos wrote:
If (trigger = true ) then trigger=false
Else trigger=true

This sounds like the liar's paradox (from ancient Greece as I recall)

Re: String Arrays

Anonymous — Tue, 10 Apr 2007 16:58:28 GMT

Not exacly

This is executed once and just changes the state of the boolean variable.

The paradox you talk goes like this: (the zinon paradox)

I am a man and i always tell the truth and i say i am lying.

This is a paradox caused by selfreferenced sentenced. Such logical sentences are not valid in mathematical first order logic.

But ofcourse the code above has nothing to do with that