Forum Replies Created
-
Posts
-
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.
James M
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.
James M
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.
James M
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 ENDIFI’m working around it by using the MS, but it is odd IMO.
James M
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).
James M
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.
James M
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.
James M
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?
James M
Never mind, user error.
But, while we’re here, can we send a message to the stair and railing group that macros within railing (and I assume stair) part objects don’t inherit the PEN directive from the calling object. If the object or macro doesn’t have its own PEN directive, parts are drawn with pen #1, which is never right for uncut pens. And to put the directive in the macro isn’t straightforward, since these macros are in use by non-railing objects too.
James M
I replied to this yesterday, but it seems it did not post. You need to create the AC_DrawingName and AC_DrawingNumber parameters – they do not come with the subtype (who knows why).
James M
AC_DrawingName and AC_DrawingNumber work, but you have to create the parameters; strangely, they are not included in the subtype.
James M
The more I think about this, it’s just wrong and we shouldn’t be concerned with it. What should happen is scripted hotspots should be associative even with no ID. And in fact, they already are, if you use the palette editing. Then I would not give that hotspot an ID, because it is in fact more reliable (no ID to change accidentally or increment wrong.)
We still have the problem of dimming to GEHs, which must have IDs. I can’t reconcile hard coded IDs with parametrics, I’ll need to try a real world case.
James M
You are correct, HOTSPOTs with IDs work. I swear I checked that, smh.
I think hard coded IDs are too weird for me, I would have to think through the contingencies of that. For the cases I am thinking of, I don’t think the incremented ID could vary.
It still makes no sense to me as a user that I can impose associativity on a point that the dim tool can’t by itself.
Thank you Barry!
James M
