topic Re: AC_TextStyle_1 strikethrough useless error in GDL

AC_TextStyle_1 strikethrough useless error

runxel — Tue, 14 Sep 2021 07:15:13 GMT

If you don't want to use a full blown PARAGRAPH, since you're happy with TEXT2 and somebody uses the strike through option in the label.... you'll will get a "Facecode Value not in Range" error for using `AC_TextStyle_1` in DEFINE STYLE.

But – it still works. So why not remove the damn error, GS?

Re: AC_TextStyle_1 strikethrough useless error

Barry Kelly — Mon, 03 May 2021 01:21:51 GMT

What is the full DEFINE STYLE command you have used for 'AC_TextStyle_1' ?

Barry.

Re: AC_TextStyle_1 strikethrough useless error

DGSketcher — Mon, 03 May 2021 01:54:51 GMT

There is a similar thing with pen numbers in that the -1 value is available but can’t be used. I found setting a Values range limit in the Parameters script clears the pen from the selection grid. Is a range limit appropriate to your face styles ?

Re: AC_TextStyle_1 strikethrough useless error

runxel — Mon, 03 May 2021 09:15:45 GMT

Barry wrote:
What is the full DEFINE STYLE command you have used for 'AC_TextStyle_1' ?

Nothing fancy, really.

define style "label_text_style" 	AC_TextFont_1, AC_TextSize_1*100/GLOB_SCALE, txt_anchor, AC_TextStyle_1

The GDL manual states, that the text style flag for subscript, superscript, and strikethrough only works with STYLE{2} – but at least strikethrough still works when set with STYLE. It only raises the error mentioned above.

Re: AC_TextStyle_1 strikethrough useless error

Barry Kelly — Mon, 03 May 2021 14:38:16 GMT

I just looked at the GDL manual and DEFINE STYLE only allows for bold, underline and italic in the face code values.
DEFINE STYLE{2} however includes extra values for superscript, subscript and strikethrough.

But I guess the problem is, DEFINE STYLE{2} doesn't include the anchor position.
And it says …

If the defined style is used with the TEXT2 command, size means character heights in millimeters, while the superscript, subscript and
strikethrough face_code values are not effective.

So I don't think there is a way around your dilemma - put up with the error message or change to use paragraphs.

But yes, it is strange (annoying) it does work, but gives you the error message.
This would be one to report to your Archicad support people.

Barry.