Péter Baksa

Forum Replies Created

Viewing 15 posts - 136 through 150 (of 224 total)
  • Author
    Posts
  • in reply to: Issue with label and surface override #4602
    Péter Baksa
    Keymaster

    Hi David,

    The dialog is correct, this is how AC works. Greyed settings don’t reflect the current state of the object, they show what will happen when the override is enabled. For example complex profile walls can have more than three different surfaces, composite wall edges can have more than one surface.

    New walls will get the tool default settings, including surface overrides. Could you describe the workflow to get the “ghost” that is not correct?

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Opening oversize no longer instantly updating #4595
    Péter Baksa
    Keymaster

    This is a bug, we added it to the list.
    You could use wallhole2 and draw the lines yourself. Or re-organize your parameters so that A/B is the wallhole size, and oversize is subtracted from that.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Issue with label and surface override #4594
    Péter Baksa
    Keymaster

    Hi,

    “but the does not update the dialogue” – what do you mean with this? What result do you expect?

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Detecting Line Intersection #4593
    Péter Baksa
    Keymaster

    Hi James,

    The direction vectors are unit vectors along the lines, their length have to be exactly 1 (meter). Compute the length of the vector between the two points on the line, and to set the vector length to 1, multiply its end coordinates by 1/length.

    If you use an EPS value that is common in GS libparts, this code has a small bug, the lines are treated parallel (no intersections) when their angle is smaller than 0.81°, which is still quite noticable. Using EPS = 0.00000001 will set the limit to 0.0081°

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Create graphical Hotspots from a marco called Object #4590
    Péter Baksa
    Keymaster

    If you need different rotations in each instance, you have to use a different parameter in each. The hotspot uses the parameter belonging to the parent object, not the macro.
    A solution for this could be that you pass an array of rotations, and an index telling which one to use from the array for the hotspot.

    An example with simpler length editing:
    parent:

    for i = 1 to 2
    	call "testmacro" parameters x = x, i = i
    	line2 0, 0, x[i], 0
    	add2 0, 0.1
    next i
    del 2

    macro:

    unID = (i - 1) * 3 + 1
    
    hotspot2 0,	0,	unID, x[i], 1 + 128	: unID = unID + 1
    hotspot2 x[i],	0,	unID, x[i], 2		: unID = unID + 1
    hotspot2 -1,	0,	unID, x[i], 3 		: unID = unID + 1

    parameters in both:
    x as length array
    i as integer

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Opening oversize no longer instantly updating #4586
    Péter Baksa
    Keymaster

    Hi Barry,

    I forwarded your question to the developers.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Create graphical Hotspots from a marco called Object #4585
    Péter Baksa
    Keymaster

    Hi Samantha,

    are you trying to make editable hotspots, or fixed ones?

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: how to get the surface name of a complex wall #4568
    Péter Baksa
    Keymaster

    Hi David,

    we added this as a bug to be fixed. Currently you can’t get the overridden surface from GDL.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    Péter Baksa
    Keymaster

    Hi Nader,

    yes, that could also work with the simple project2. Or you could project2{3} … parameters … twice.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    Péter Baksa
    Keymaster

    Parameters and variables set in the 2D script doesn’t get through via project2 to the 3D script.

    You can define cutplanes in the 2D script using the PROJECT2{4} command. Unfortunately it has a bug, so it doesn’t show correct cut fills from the 3D model. You can set a cut fill override if you need only one cut fill.

    You can also use PROJECT2{3} with PARAMETERS, setting a hidden parameter whether you need the cutplane or not.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Polygon Operations extension #4558
    Péter Baksa
    Keymaster

    Hi Ashley,

    This is an add-on shipped with AC, each user gets it.
    It is used for example in “Kitchen Layout”.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Value liste as text instead of numbers? #4543
    Péter Baksa
    Keymaster

    David, that’s intentional, this way it is possible to include quotation marks in a string.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Checking library for file names #4542
    Péter Baksa
    Keymaster

    Hi Shaun,

    no currently it’s not possible.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: DESCTIVATING A CUTPLANE FROM 2D SCRIPT or similar method #4538
    Péter Baksa
    Keymaster

    Hi,

    in 3D script, GLOB_VIEW_TYPE is 2 when the 3D script is run for project2. That’s what Barry’s example does, too.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

    in reply to: Value liste as text instead of numbers? #4536
    Péter Baksa
    Keymaster

    Hi all,

    a more flexible way is to use the VALUES{2} command.

    set parameter “iVal” as integer

    master script:
    dim aVal[], sVal[], picVal[] ! parameter value, string shown on UI, icon index shown on UI
    aVal[1] = 1 : sVal[1] = “Option 1” : picVal[1] = 2
    aVal[2] = 2 : sVal[2] = “Option 2” : picVal[2] = 1

    param script:
    values{2} “iVal” aVal, sVal

    ui script:
    ui_infield{3} iVal, x, y, w, h,
    2, ! pop-up with icons
    picture_name,
    images_number,
    rows_number, cell_x, cell_y,
    image_x, image_y,

    picVal, sVal, aVal

    This way you can easily re-organize the strings in the popup, by re-ordering the aVal, sVal, picVal arrays. You can rename the strings or swap icons by changing just one line in the master script.

    Péter Baksa
    Library Platform, Software Engineer
    GRAPHISOFT SE

Viewing 15 posts - 136 through 150 (of 224 total)