Péter Baksa

Forum Replies Created

Viewing 15 posts - 106 through 120 (of 224 total)
  • Author
    Posts
  • in reply to: Variable Mismatch #4788
    Péter Baksa
    Keymaster

    Hi, is this in a parameter script? Are these variables or parameters?

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: PROFILE REQUEST PARAMETER SCRIPT #4785
    Péter Baksa
    Keymaster

    Hi,

    No, but a profile type parameter shows it’s default size in the UI popup (and the request is usable in UI script).

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Section Marker Linetype #4781
    Péter Baksa
    Keymaster

    Hi, no, GDL doesn’t know that.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Request Object Parameters with Label #4778
    Péter Baksa
    Keymaster

    Hi,

    bDoor = “” initializes the variable as a string, bDoor = 0 as numeric. It could cause a problem if the request fails, and you compare an integer against the string variable.

    All the variables are needed in the request expression, altough you can use shorter names for the unneeded ones.

    The last parameters expression is not needed, your bDoor is a variable.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: AC_​Sill_​To_​Curr_​Story: Bug or Not? #4764
    Péter Baksa
    Keymaster

    There is a workaround until it is fixed:
    A property can be set up to be based on an expression. For this expression you can select parameters that are the same as in IES. You can display the evaluated
    expression with Classification and Properties Label.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: AC_​Sill_​To_​Curr_​Story: Bug or Not? #4763
    Péter Baksa
    Keymaster

    Yes, we know about it, this is definitely a bug.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Text rotation in labels #4757
    Péter Baksa
    Keymaster

    Hi,

    Read about controlling labels here, label ac_ parameters here, label globals here.
    If you need it to remain horizontal independent of plan rotation, use the “View_Rotangle” request.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: GDL: MULTIPLE COMPLEX PROFILES #4750
    Péter Baksa
    Keymaster

    Hi, please post a sample code.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Sectatrs and so on in Skylights? #4746
    Péter Baksa
    Keymaster

    Hi, it works for me. Can you give a short example? Which AC version? Floor Plan or Section?

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Railing Panel info #4738
    Péter Baksa
    Keymaster

    No, there isn’t. Use the offset settings of the panel, and it will be automatically smaller.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Railing Panel info #4735
    Péter Baksa
    Keymaster

    Sorry, I didn’t notice the name of the global. It’s the set of global variables starting with RAILINGPANEL_ that you need.

    With somewhat custom settings, it is possible that a panel has more than four sides (panels connecting with different heights at a landing, or columns offset from the end of the landing: the corners might be cut off with horizontal planes). To handle these cases too, there is RAILINGPANEL_GEOMETRY that is the contour polygon, and RAILINGPANEL_UNCUT_GEOMETRY that is a four-sided polygon before the cuts.

    RAILINGPANEL_FLAGS[i][2] tells which side of the panel is the i-th edge (1 – bottom, 2 – end, 3 – top, 4 – start) You can derive the height from RAILINGPANEL_UNCUT_GEOMETRY start/end edge.

    The slope can vary on a winding stair. RAILINGPANEL_GEOMETRY can have multiple segments on the top/bottom sides. For wires, the average slope can be computed from the first point of the bottom side and the first point of the end side of RAILINGPANEL_UNCUT_GEOMETRY.

    Slanted/skewed railings (RAILINGPANEL_SLANT_ANGLE, RAILINGPANEL_SKEW_ANGLE) need to be handled carefully.
    Curved panels are also special: RAILINGPANEL_TYPE tells the overall shape of the railing. You might not want to handle curved panels at all.
    Curves are given in a format similar to PolyOperations: start x, y, central angle.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Railing Panel info #4731
    Péter Baksa
    Keymaster

    Hi, the stair and railing globals don’t contain useful data in the libpart editor, you have to place the element.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: TUBE twisting #4729
    Péter Baksa
    Keymaster

    Looks like TUBE{2} can’t do it.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Forward Migration #4725
    Péter Baksa
    Keymaster

    The migration is always run in the newer version of AC, on the new object. The old one doesn’t know anything about the new one. Old libpart GUIDs are listed in the migration table. When a library is loaded, all libparts’ migration tables are read and checked against placed objects.
    Backward migration happens when saving as previous version .pln: the parameter list is saved with the GUID in the migration table listed at that version.
    Some information about migration can be shown: in the Library Developer Menu select Log the Migration Process (then re-open the non-migrated file).

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Forward Migration #4721
    Péter Baksa
    Keymaster

    Let’s quote that mention from AC-Talk here too, maybe it will be easier to find.

    Automigration is a special type for migration: it simply does an ID change, without running migration scripts. It is useful to eliminate migrations from new elements, and create step-by-step migration logic through many versions.
    _________________
    Gergely Fehér
    Team Leader, Library Team
    GRAPHISOFT SE

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

Viewing 15 posts - 106 through 120 (of 224 total)