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

[Dominika Bobály]

Unfortunately it is not working that way, yes. You have to put all corresponding parameters into both objects to make edit and parameter value transfer work both ways.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

Doug,
the fast solution to your problem is to unlock the “All parameters” list in windows: open your saved window, find the macro call for “gs_general_window_macro”, open that macro, and look for the macro call for “GS Corner Window Functions” (or “GS Window Functions” in some cases) in its parameter script. Open it, and comment the hideparameter all line in its paramscript (don’t forget to save: probably the easiest way to do this is to extract the library lcf to make it all writable). This will give you the All Parameters list back, where you can look for your new parameters.
To add them to the UI: if they are property parameters, I would insert them into the already existing Descriptions page (the macro of it is in “gs_general_window_macro”, called “ui_Description_m”, look for it in the UI script). Your new parameters should be added to the macro as well, and must be taken care of in the UI script of the macro, similar to the other, existing property parameters.
Hope this helps. Ask, if you need more specific assistance, or you want to create a separate page for your new parameters only.

Attachments:

1. 

   AllParamList_forum_AC19.png
   

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

More about the complete parameter list hiding is here (end of the topic). I should really link this to the UI section of Learning as well:)

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

Doug,
not sure if I understand right.. the All Parameters List option is not really removed, we just started to use the hideparameter command (with the all parameter) to omit it in most of GRAPHISOFT’s objects for better-looking interfaces. This is optional. If you create objects only using the All Parameters list, that’s fine. If you want to have an UI along the All Parameters list, that is also possible (without doing anything special). The special thing is only needed to hide the list (hideparameter command).
If you need further info, give me an example or a more detailed specification. Thanks.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

It is not possible to put pages outside of the Custom Settings group in AC18. You can only add pages within that (see my other reply).

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

The screenshots were taken in AC18, right? If so, do the following steps:

1. from the master script of the door, open “gs_general_lt_door_macro” macro
2. look for ! Tabpage Structure Definition part of the UI script in the macro
3. find the last tabpage definition (which is the Parameters for Listing in general, displayed in every DW object):

   gs_stUI[i] = titleListing:				gs_icoUI[i] = "ui_tabpage_listing(13)":				gs_idUI[i] = 0: i=i+1
   

4. duplicate it with copy-paste, and fill up according to your new tabpage, for example:
   gs_stUI[i] = “My Tabpage Title”: gs_icoUI[i] = “nameOfMyPageIcon”: gs_idUI[i] = 0: i=i+1
   Leave the gs_idUI[i] with 0 value. The “GS Door Functions” macro handles the pages with fix IDs (non zero), while the rest of the pages get their ID in the returned parameters of the macro call in variables like myPage_9. There are 20 slots for extra pages. Just add a new return value for your new page, myPage_10 in doors, for example. That will be the last used index.
5. look for the variable myPage_ListingId in the script, and wherever you find it with value assignation, do the following (in cases you want to insert your page, depending on the existing conditions):

   myPage_ListingId			= myPage_9
   myPage_NewPageId			= myPage_10 !always the next index after the listing one
   

6. Do this in all the needed places. This ensures the continuous indexing of pages, so the Prev-Next buttons will work for your new page as well. I think the best is to include it into every condition to make sure (7 or 8 places alltogether).
7. look for the line if myPage_ListingId > 0 then. This is a condition to show the Parameter for Listing page. Copy-paste the whole condition, and modify to fit your new page:

   if myPage_NewPageId > 0 then
   	ui_page myPage_NewPageId
   	! your UI script here
   endif

You can either code the content of the page there, or create a macro and call it from within the condition.

This should work for AC18. Look for similarities in window macros as well (almost the same).
If you need solution for AC19, let me know, because that is a lot different (and a bit more flexible).

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

You can find a tutorial and downloadable examples (with the correct use of displayParam as well) in this lesson of the Learning section. The displayParam is not always necessarily the edited parameter. It can be any other parameter represented, but the connection between the edited and represented ones should be handled in the parameter script of the object. Check out Central editing example AC19.gsm in the downloadable lcf for example codes.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

The complete list of parameter script-restricted requests can be found here, in case you were wondering about the rest of them.
The GDL compatibility guide is available for download on this site as well, check here.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

James,
this global has one column and a number of rows equal to the skins number, so the form is:
WALL_SKINS_BMAT_NAMES[nSkins][1]

The WALL_SKINS_NUMBER global returns the filled rows number of WALL_SKINS_BMAT_NAMES, and you can use it for running the iteration.
Try the following code (copy it to a window’s 2D script):

text2 0, 2, "vardim1(WALL_SKINS_BMAT_NAMES) = "
text2 7, 2, vardim1(WALL_SKINS_BMAT_NAMES)

text2 0, 3, "vardim2(WALL_SKINS_BMAT_NAMES) = "
text2 7, 3, vardim2(WALL_SKINS_BMAT_NAMES)

text2 0, 4, "WALL_SKINS_NUMBER = "
text2 7, 4, WALL_SKINS_NUMBER

for ii = 1 to WALL_SKINS_NUMBER
	text2 10, ii*1, WALL_SKINS_BMAT_NAMES[ii][1]
next ii

The PRINT command iterates through any array global without worrying about the array dimensions, that’s why it was working.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

We extended the request description with the keyword here on the site, thanks for finding this inconsistency.
Please, check the search option again, hope it lists this feature now.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

The “view_rotangle” request option can return that angle:
REQUEST (“view_rotangle”, “”, angleViewRotation)
See Requests in GDL manual.
We already use it for always readable texts, see this post in Tips&Tricks.
Hope it helps.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

Anton, Kristian,

thank you for your enthusiasm, we really hope we can live up to the expectations:).
The learning materials are being constantly updated and extended as we go.
In case you have any related questions or recommendations to any post or lesson, please, share in the post’s comments, so we can make them better.
Good to know there are fellow GDL developers “out there”.
Welcome:)

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

The 2D script may be running when MVO is “Show Opening Only” for calculations, but the actual drawing display function is somewhat limited in that case (but still no information comes from the program to the object about this condition).
When the MVO is “Hide on Floor Plan”, the object’s scripts are not running at all (Frank guessed right), so no way of checking this from within the object.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

A “command and function pool” was added to the end of posts (and some lectures), with links. Hope it helps.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Dominika Bobály]

Corrected, thanks for the notice.

Dominika Bobály
Product Manager
GRAPHISOFT SE

[Author]

Posts