For the bevel case you get a better result by using the roof() operator.
And from this there is a more or less stony path to calculate sloped
slices to get a better approximation ...

intersection()
{
  scale([1,1,2])
  roof(method = "straight", convexity=10)
  D()
  {
    offset(.5)txt();
    offset(-2)txt();
  }
  cube([400, 400, 3], center=true);
}

Am 31.10.2025 um 19:30 schrieb Jordan Brown via Discuss:

I can't find "roof" in the OpenSCAD cheat sheet, and you show no
importing or including of other files, so I am mystified.

Jon

On 11/21/2025 10:01 AM, Rudolf via Discuss wrote:

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com

Thanks.

I notice that the documentation is still referring to the named items in
OpenSCAD as "variables".  Small wonder so many new users crash headlong
into this misunderstanding.

Is there any nomenclature we can use instead of "variable"? Identifier? 
Even "constant" might be better

Jon

On 11/21/2025 7:04 PM, Michael Marx (spintel) via Discuss wrote:

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com

In functional programming, they’re called variables, despite their
immutability. I think we are stuck with the term.

On Fri, Nov 21, 2025 at 8:38 PM Jon Bondy via Discuss <
discuss@lists.openscad.org> wrote:

On 11/21/2025 6:40 PM, Father Horton via Discuss wrote:

Perhaps more importantly, different runs through the same snippet of the
program may have different values for the same name.

for (i = [0:10]) echo(i);
function inc(j) = j + 1;
module kube(k) cube(k);

Are i, j, and k variables or constants?

(OpenSCAD behavior actually aligns with the C/C++ "const" modifier, but
I think that expecting OpenSCAD users to be familiar with C or C++ is a 
stretch.)

If those working in functional programming choose to call immutable
values "variables", that is unfathomable and incorrect, but I don't
think we need to adopt or encourage that misleading nomenclature.

I agree that SOME of the named values that we use are actually
variables, while most of them are immutable.  This, of course, only adds
to the confusion.  We could attempt to manage this in the documentation
by specifically calling THOSE values "variables", and noting the
difference.  I assume that none of the proposed language changes will
create actual variables, but I could be wrong.

The term "named constant", however awkward, seems to capture how
OpenSCAD works, and does not require a knowledge of C or Pascal or
Modula2, all of which have "const"s.

If we keep writing documentation referring to named constants as if they
were variables, then we should not be surprised by on ongoing confusion
by new adapters, and perhaps by some who give up on OpenSCAD because of
their confusion and frustration.  If that is an acceptable penalty to
pay for the simplicity of the term "variable", then let's proceed with
no change

Jon

On 11/22/2025 1:33 AM, Jordan Brown via Discuss wrote:

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com