Forum Replies Created
October 9, 2018 at 11:17 in reply to: AC22 new Label fixed parameters #4282
Thanks for the notes Geoff, we have these ones already on our todo list.
Let us know if you find something else we missed!
GRAPHISOFT SESeptember 4, 2018 at 15:20 in reply to: "Creating a Label Text" tip page needs update #4252
we are working on the update, but in the meantime a note was added to the article you mentioned, with a short explanation of what to look up while waiting for the new entry:).
The general logic of text handling did not change in labels, only most of the globals were turned into parameters.
GRAPHISOFT SESeptember 4, 2018 at 15:03 in reply to: AC22 new Label fixed parameters #4250
Piotr is right, the new global variable LABEL_HAS_PONTER provides info about the pointer on/off state. We use that in the condition for the 2 symbol types.
It is the same as the old (deprecated) LABEL_CUSTOM_ARROW – but the meaning is reversed (OFF used to mean value 1 in the old global, and now it returns 0, and vice-versa).
GRAPHISOFT SEAugust 31, 2018 at 10:27 in reply to: AC22 new Label fixed parameters #4243
first, it is lovely to hear you like the new additions of text handling.
1. Add/Remove Pointer locking: this was left out intentionally, by design. We did not want to create a parameter for Pointer control, we kept it as a Global variable (with a more suitable name), therefore no locking option. The automatic pointer-drawing function is one of the basic features of any label, can make a symbol label work similar to Text/Autotext Labels. Also, keeping it out of the parameter list saves the trouble caoused by multi-selection. Usually we script our symbol labels to have a simpler text format suitable for the Pointer ON version, too, and it is recommended you do the same.
2. The basic idea long ago was to have this “Uniform Pen” to overwrite in display all pen settings of an element. It is supposed to work as you expect it: to deal with the poly2 contours and fill pens as well. This is a bug, thanks for letting us know about it.
GRAPHISOFT SEJuly 19, 2018 at 13:14 in reply to: Stair Tool: integrated tread and risers #4193
If you create a custom stair with the tool and select it (in 2D or in 3D), the general opening methods for library parts should work. The “Open object” command opens all stair-related library parts of the placed element (multiple ones). If you wish to open just one single object, you can use the Report window: type the exact name of the libpart you wish to edit, select the text and use the “Open object” again (or the hotkey).
GRAPHISOFT SEJuly 11, 2018 at 13:15 in reply to: Requesting platform, mac or windows #4184
Pressed the wrong reply, see some info below Joachim’s post:)
GRAPHISOFT SEJuly 11, 2018 at 13:06 in reply to: Requesting platform, mac or windows #4181
thanks for the uploads. We are aware of the issue with ui_infield: before AC 22, there was no correct way to set up a multi-row image control for the same parameter. Viable workaround does not really exist (not even with method 4): ui_infield does not tolerate well if parts of the valid parameter value range are omitted from the UI control.
Since we also had issues with this, for AC 22 new interface commands were introduced to make the layout possible: UI_PICT_RADIOBUTTON.
You can create a mosaic-image with pushable parts (note, only one part can be selected in this case).
If you want multiple parts of the mosaic to be pushable at the same time (booleans), you can use the UI_PICT_PUSHCHECKBUTTON the same way.
Just ignore the preview overlap warnings if you want to have a continuous mosaic image:).
Enclosed are the resulting controls on both platforms.
Is this what you want it to look like? I used this cross image to check on the image edges.
GRAPHISOFT SEJuly 10, 2018 at 10:20 in reply to: Missing Label commands in 22 GDL guide #4178
Also, we have a “new features guide” to give you some general overview of changes in ARCHICAD 22, see here, please.
GRAPHISOFT SEJuly 10, 2018 at 10:17 in reply to: Missing Label commands in 22 GDL guide #4177
Most of the label global variables are considered deprecated starting from AC22.
For the complete list of them, see here.
In the meantime, lots of fix named optional parameters have been introduced to continue the role of the deprecated globals:
– label specific ones are here
– text handling related general ones (for all annotation elements) here.
So, the above is the reason why the updated GDL Reference Guide does not contain the same stuff as the previous one.
Hope this helps.
GRAPHISOFT SEJuly 6, 2018 at 12:25 in reply to: Requesting platform, mac or windows #4164
officially any library part is considered platform-independent, so there is no built-in way within GDL to “know” about the platform.
Could you upload here a win-mac comparison image of the issue you are experiencing with ui_infield? With example code, if possible.
As far as I know, there should be only very small differences, mostly in connection with the control layouts “borrowed” from the platform’s op. system itself. If you see something very different, maybe it’s a bug so I would like to check.
Or maybe we can suggest a workaround:).
GRAPHISOFT SEMay 11, 2018 at 09:48 in reply to: Layout size #4076
there are 3 fix named optional parameters containing data about the layout and the drawing. These are only available in the drawing title objects themselves. (not sure why do you want to request this info elsewhere?).
AC_LayoutRect: Length – one-dimension array with 5 rows. Contains the geometry definition of the Layout´s bounding rect (measured in the Drawing Title object´s coordinate sytem)
- AC_LayoutRect lower left corner X
- AC_LayoutRect lower left corner Y
- AC_LayoutRect upper right corner X
- AC_LayoutRect upper right corner Y
- AC_LayoutRect direction angle (The bottom side´s angle of the rect. Measured in the Drawing Title object´s coordinate system. 0 <= angle > 360)
AC_GridRect:Length – Contains the geometry definition of the Cell´s bounding rect. The structure is same as with the AC_LayoutRect.
AC_DrawingRect:Length – Contains the geometry definition of the Drawing´s bounding rect. The structure is same as with the AC_LayoutRect.
You can check examples for them in any of the shipped INT Drawing Title objects (Framing Title for example).
I’m adding this topic to the “things we need to document better” pile now:).
In the meantime, hope this info helps!
GRAPHISOFT SEMarch 26, 2018 at 09:25 in reply to: MVO page not displaying info correctly #3960
second run of trying to post here, so in case you see a duplicate, that was me.
So, could you send us a sample of the problem? I failed to reproduce it with the latest official AC21 build. In case you do not want to upload here, write to the GDL Center email.
GRAPHISOFT SEJanuary 18, 2018 at 10:09 in reply to: GDL web addon #3735
The plugin you are looking for is discontinued. We switched to WebGL (see on BIMcomponents.com), but parametric configuration from browser is no longer an option.
GRAPHISOFT SENovember 10, 2017 at 15:21 in reply to: Force Refresh of Objects using LIBRARYGLOBAL #3664
Debugging MVO returned values: we usually use text output commands (text2), to check on it, or you can try PRINTing it into the report window.
Never should it be stored in a parameter.
Glad you could handle the issue.
GRAPHISOFT SENovember 8, 2017 at 12:14 in reply to: Force Refresh of Objects using LIBRARYGLOBAL #3659
first, let’s assume you did not try to save the returned value of the MVO request in a parameter in any way, because that may cause problems like you described.
Here is a tutorial on how to correctly implement an MVO object, and how to link it to a placeable object via LIBRARYGLOBALS request.
Here is another article about the topic, in general.
In case the articles do not give you a solution to your problem, we can discuss this further.