From 0e2a8aa9ec13bbb20624c14db03d418f4e1fabcf Mon Sep 17 00:00:00 2001 From: jmespadero Date: Fri, 28 Jul 2023 10:24:02 +0200 Subject: [PATCH] link to muparser help --- src/meshlabplugins/filter_func/filter_func.cpp | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/meshlabplugins/filter_func/filter_func.cpp b/src/meshlabplugins/filter_func/filter_func.cpp index dde18d949..bfe4fe2bd 100644 --- a/src/meshlabplugins/filter_func/filter_func.cpp +++ b/src/meshlabplugins/filter_func/filter_func.cpp @@ -120,20 +120,22 @@ QString FilterFunctionPlugin::pythonFilterName(ActionIDType f) const } const QString PossibleOperators( - "
It's possible to use parenthesis (), and predefined operators:
" + "
It's possible to use parenthesis (), and predefined " + "muparser built-in operators, like:
" "&& (logic and), || (logic or), <, <=, >, >=, " - "!= (not equal), == (equal), _?_:_ (c/c++ ternary operator)

"); + "!= (not equal), == (equal), _?_:_ (c/c++ ternary operator).

"); const QString PerVertexAttributeString( - "It's possible to use the following per-vertex variables in the expression:
" + "It's possible to use muparser built-in functions" + "and the following per-vertex variables in the expression:
" "x,y,z (position), nx,ny,nz (normal), r,g,b,a (color), q " "(quality), vi (vertex index), vtu,vtv,ti (texture coords and texture " "index), vsel (is the vertex selected? 1 yes, 0 no) " "and all custom vertex attributes already defined by user.
"); const QString PerFaceAttributeString( - "It's possible to use the following per-face variables, or variables associated to the three " - "vertex of every face:
" + "It's possible to use muparser built-in functions" + "and the following per-face or per-vertex variables:
" "x0,y0,z0 for the first vertex position, x1,y1,z1 for the second vertex " "position, x2,y2,z2 for the third vertex position, " "nx0,ny0,nz0 nx1,ny1,nz1 nx2,ny2,nz2 for vertex normals, r0,g0,b0,a0 r1,g1,b1,a1 "