James Murray

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 61 total)
  • Author
    Posts

  • James Murray
    Participant

    There’s also extreme copies of a lot of property objects.

  • in reply to: Trying to understand autoscripted groups #4248

    James Murray
    Participant

    I don’t have any trouble understanding how to handle the code. I’m curious about the process.

  • in reply to: ASSOCLP_​PARVALUE_​WITH_​DESCRIPTION #3996

    James Murray
    Participant

    Gergely, I’ve submitted this as #244744. I would have PM’d you but I didn’t see the option.

  • in reply to: ASSOCLP_​PARVALUE_​WITH_​DESCRIPTION #3966

    James Murray
    Participant

    Anything more on this?

  • in reply to: ASSOCLP_​PARVALUE_​WITH_​DESCRIPTION #3941

    James Murray
    Participant

    Thanks, I’m getting closer. The array dump works. How do I capture just the description? I get an error if I try to set a variable equal to p_values_and_descriptions[1][1], for example.

  • in reply to: ASSOCLP_​PARVALUE_​WITH_​DESCRIPTION #3939

    James Murray
    Participant

    One more try. open square bracket i close square bracket open square bracket j close square bracket. Maybe it did the same thing to your text. Thanks again for the help.

  • in reply to: ASSOCLP_​PARVALUE_​WITH_​DESCRIPTION #3938

    James Murray
    Participant

    Again what I post does not show up. I was trying to say the text2 line needs to refer to p_values_and_descriptions[i][j], not just [j]. (Incidentally, I tried to bold the [i].)

  • in reply to: ASSOCLP_​PARVALUE_​WITH_​DESCRIPTION #3936

    James Murray
    Participant

    Thanks, Gergely, but I’m not getting it. I did notice the TEXT2 line needs to be text2 j, i, p_values_and_descriptions[i][j]. But the label is still empty when applied. I’ve attached a simple test case.

  • in reply to: Name_​of_​material #3842

    James Murray
    Participant

    I’ll add that ‘useless warnings’ train the user to ignore all warnings, which will certainly include serious warnings eventually. My policy is to eliminate such errors entirely. Since GDL never substantively improves, it would be great it didn’t gradually get worse.

  • in reply to: Name_​of_​material #3833

    James Murray
    Participant

    This is the Surface Viewer that shipped with AC11, which only started giving errors in AC21. The error occurs if there are unused IDs in the the surface attributes.

  • in reply to: Double adding to parameter #3806

    James Murray
    Participant

    Thanks, Barry , I thought it had to do with multiple executions. Strangely, it works correctly now when placed in the Master (adding and subtracting with the checkbox), but in the Parameter script the identical code always subtracts.

    rrr = APPLICATION_QUERY ("parameter_script", "firstoccasion_in_progress", isFirstRun)
    IF isFirstRun THEN
    	IF GLOB_MODPAR_NAME = 'bOption' THEN
    		IF bOption THEN
    			ZZYZX = ZZYZX + optionThk
    			PARAMETERS ZZYZX = ZZYZX
    		ENDIF
    		IF NOT(bOption) THEN
    			ZZYZX = ZZYZX - optionThk
    			PARAMETERS ZZYZX = ZZYZX
    		ENDIF
    	ENDIF
    ENDIF

    I’m working around it by using the MS, but it is odd IMO.

  • in reply to: Section Marker Tail #3800

    James Murray
    Participant

    I have mine offset from the origin — the line meets the corner of the triangle. The built-in one uses a masking fill inside the circle. (It’s the window background color by default, making it impossible to see).

  • in reply to: Section Marker Tail #3766

    James Murray
    Participant

    A section marker is drawn twice — the second time it is mirrored, and the SYMB_MIRRORED global is 1. By testing this global you can draw the head and tail once each. Then I have a checkbox parameter to flip the head and tail if desired.

  • in reply to: Solid ops and subroutines #3710

    James Murray
    Participant

    Wow that formatting looks great. Never mind. If you want to use an ADDGROUP result in a subsequent SUBGROUP operation, you can’t do the ADDGROUP in a subroutine. It would be nice to know why.

  • in reply to: Railing Tool subtypes #3673

    James Murray
    Participant

    More info: I am passing a pen parameter to the macro. It seems that SYMB_VIEW_PEN does not work in this context, the global variable returns 1 and that is the pen the macro uses. When I changed to PARAMETERS useThisPen = myPen, the macro correctly used myPen. It seems some object globals don’t work within railings?

Viewing 15 posts - 1 through 15 (of 61 total)