Gergely Fehér

Forum Replies Created

Viewing 15 posts - 166 through 180 (of 249 total)
  • Author
    Posts
  • Gergely Fehér
    Keymaster

    Tony,
    You should not call our chairs from your library – as the chairs are placeable objects. Please never use placeable elements as macros, it can cause many problems.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Project Info – REQ? #2258
    Gergely Fehér
    Keymaster

    You can reach detailed project info via autotext only, so you can’t use those values in GDL script at the moment.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    Gergely Fehér
    Keymaster

    There is an application query for image files and ies files. Listing the whole library seems to be a bit useless, as normally there are thousands of libparts loaded. Why do you need that?

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: ID of layout #2250
    Gergely Fehér
    Keymaster

    To convert strings to numbers, you can use the SPLIT function.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Determining which tool and setting are selected #2237
    Gergely Fehér
    Keymaster

    Linking to tools is based on subtypes only. Elements under the “Section Marker” can be used with the section tool, and elements in the “Elevation Marker” can be used with the elevation tool. Section-Elevation marker subtype is the common ancestor of them, and as in early ARCHICAD versions it was one tool the elements of this subtype appears in both of the new tools.
    To determine which of them is used, I would make 2 copies of the object, save them as different section and elevation markers and save the original item as a macro. Both of the new elements should simply call the common macro, with adding one more parameter: the information about the callers subtype

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Accessories addon #2230
    Gergely Fehér
    Keymaster

    Heimo,
    Introducing polyline input and working methods to GDL objects is a much better idea, than upgrading the old accessories – but it is a quite complicated issue. It is on our list for a few years, but still had no time to design in depth and develop it.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: ID of layout #2229
    Gergely Fehér
    Keymaster

    I think there is no solution for that in GDL, as you can’t reach the value of the layout id.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: GLOB_​ changes #2212
    Gergely Fehér
    Keymaster

    Bruce,
    There is no workaround for automatical locking of parameters when settings dialog is closed. We do not want to support this kind of workflow, as this can cause other problems in the program. As we declared earlier – before the release of 19 – context and view dependent information must not be used in parameter script.
    Instead of automatic locking, all the objects parameters should be controlled by the script writer: GLOB_MODPAR_NAME, parameters and values commands enables the developer to take control of the possible parameter values and ranges, so in a well written library part geometry should not fail by a user setting.

    Barry,
    The other mentioned problem – GLOB_CONTEXT in the editor – is not the same! We don’t think that “invalid” values should be set in the editor – for these problems you should use the xml source format with the “meaning” technology built in the lp_xmlconverter, which provides the correct values of all parameters in all cases.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Profile picture / avatar #2211
    Gergely Fehér
    Keymaster

    We use Gravatar, check it here: https://gdl.graphisoft.com/gdl-news/avatars-in-the-forum-2/

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: ID of layout #2203
    Gergely Fehér
    Keymaster

    Hi,
    As layout id can be reached as an autotext, you can not read it’s actual value in GDL script. But, if you want your layouts to start from 23, you can set that in the layout book settings.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: GDL door and window parameters related to zones #2202
    Gergely Fehér
    Keymaster

    Hi David,
    As I tested it it seems the same to me – or I’m just testing some other parameters 🙂 Could you please send me a sample file with a door and a window between 2 zones and a schedule in mail to gdlcenter@graphisoft.com ? Please describe the problem in the file. Thanks in advance.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Accessories addon #2198
    Gergely Fehér
    Keymaster

    As it is written on the goodies download site: “Goodies are Add-Ons to ARCHICAD that are based on legacy code which GRAPHISOFT does not support anymore. You can use it ‘as is’, but be warned that they might not function properly, and they will not be fixed or upgraded.”

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: GDL door and window parameters related to zones #2193
    Gergely Fehér
    Keymaster

    David,
    As I know, windows in the AC19 INT library has this functionality too. Can you tell me which version did you try?
    gs_list_location has nothing to do with the zones – it is just a parameter for listing, users can write anything to that parameter. You can read more about linking zones and openings here: https://gdl.graphisoft.com/tips-and-tricks/linking-openings-to-zone/

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Value{2} and put functions please #2148
    Gergely Fehér
    Keymaster

    Wesley posted the right solution, you can use arrays as the parameters of the values{2} command. The only limitation is that you should use array pairs with the same dimensions.
    You can combine these 2, and you can add more than one array pair to a values{2}.

    Example:
    values{2} “myparam” numarray1, stringarray2, intvalue1, stringvalue1, numarray2, stringarray2

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    in reply to: Hotspot problem with PGON{2} e PGON{3} in solid operation #2135
    Gergely Fehér
    Keymaster

    Unfortunately there are no workaround for that, it is a bug in ARCHICAD. We will try to fix it in an upcoming update and in the next version.

    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

Viewing 15 posts - 166 through 180 (of 249 total)