Forum General discussions About this site Problems and solutions in GDL Forum rules and functions

[James Murray]

That’s… interesting? I’d rather they just fixed it. Thanks for looking.

James M

[James Murray]

OK, here’s the code since it’s not showing:

hA = A/2

PRISM_ 7, 1,
0, 0, 15,
A, 0, 15,
A, B, 15,
0, B, 79,
0, 0, -1,

hA, hA, 900,
hA/2, 360, 4013

James M

[James Murray]

In the case of an Option Set property that allows multiple choices, is there a way to offer the user the options that are in use by the element, so they can choose which option the label displays?

James M

[James Murray]

I don’t see anything in the globals or requests.

James M

[James Murray]

Hi Laura, I’m going to keep looking at it, but I have a bad feeling. The stamp explicitly does what isn’t allowed: Using parameters to store view(scale)-dependent data. It needs the scale to fill the arrays (alt_text etc), and the arrays have to be parameters to preserve the data in placed instances. This kind of clever hack of parameters is what got killed by the new rules.

I can imagine a simplified version of it that offers a few scales, and the user just has to know what parameters to use for each scale. (Sadly no, you can’t HIDEPARAMETER based on scale either.) I don’t think we can fill in one blank and populate the arrays. It’s not a problem to have graphical editing to move the symbol at different scales – that can be all 2D script.

James M

[James Murray]

I found it. I was setting a flag in a subroutine that was leaking out into another routine. But thank you for checking so closely, it motivated me to check more carefully.

James M

[James Murray]

Thank you Dominika, I did see the notice on the other question and I meant to thank you for it. It was very clear and I have already made a lot of progress.

James M

[James Murray]

No, I spoke too soon.

James M

[James Murray]

This solved it, though I don’t see why:

DIM junkArray[]
PUT 0, 0, 15,
... x3
0, 0, -1

FOR k=1 TO NSP
junkArray[k]=GET(1)
NEXT k

CALL theMacro PARAMETERS array2=junkArray, etc

Happy to dismiss the error, but I don’t see why one value in the array wasn’t enough.

James M

[James Murray]

That could be the hint I needed. Thanks Joachim.

James M

[James Murray]

I hope that Categories will be covered by this article as well. There is something missing between GetParameterFolderNames and GetParameterNames in the manual. I don’t see where folderNamesArray becomes 2 dimensional, or what the i is supposed to mean.

James M

[James Murray]

Update: The error is only in the editor, in the placed label the value text comes through.

James M

[James Murray]

Thanks Dominika, with that hint I have made some progress. I have the property chooser working in the UI script. (Though the ui_outfield seems to show the ‘hiddenID’, while the names are shown in the list. I worked around this by making the hiddenID the same as the name.)

Now I am stuck again on Property_Value_Of_Parent. I have figured out how to get the property ID which corresponds to the chosen property name. According to the ref guide, the value is returned in an array ‘propertyValues’. The value is in there; I can use PRINT to see it, and there is no other data printed. Vardim1 reports that the array dimension is 1, yet this:

sPropContent='' ! init
sPropContent= propertyValues[1]

gives an error of ‘Index value greater than array dimension’.

Thanks again, looking forward to the article.

James M

[James Murray]

Thank you! I don’t know what I was doing wrong but it worked when I rebuilt from your example.

James M

[James Murray]

That tiny difference can be evaluated, but now I see that changing the paragraph alignment and text block anchor seems to have no effect when the label is connected on the left. I’m using 3 for the paragraph alignment, and 6 for the textblock anchor. But the text looks the same as when I use 1 and for the right-side version.

James M

[Author]

Posts