> Also,
>
> Don't forget that high hierarchy/context @variables can be overwritten
> variables defined by the user or lower contexts.
>
> You can't do that with a function.
yep, I'm a big fan of overwriting variables in different contexts :)
___
Also,
Don't forget that high hierarchy/context @variables can be overwritten
variables defined by the user or lower contexts.
You can't do that with a function.
A quarta, 8/07/2020, 15:01, matteo escreveu:
> Thanks Andreas and Harrissou for the clarification.
>
> Actually what is confusing me
Thanks Andreas and Harrissou for the clarification.
Actually what is confusing me is that the variable @current_feature is
suggested in bold directly in the Expression Builder within the
Attribute Forms.
I know that variable depends on the scope (e.g. @symbol_color) but I
thought that IF a
Hi,
The @current_feature is, according to the doc[0], available when editing in
attribute table and form contexts which are not actually the one you have,
Matteo.
[0]
https://github.com/qgis/QGIS/blob/master/src/core/expression/qgsexpression.cpp#L861and
in documentation
Hi Matteo,
The "$" prefix marks a function without arguments, "@" are variables.
Sometimes both variants exist, as you have discovered. Mainly due to
historic reasons and the fact that the "$"-stuff is around for a lont
time already, but the variables where added quite a bit later.
Are you
Hi all,
before to file a ticker I'd like to have a small feedback. Maybe I'm
missing something but what is actually the difference between
$currentfeature and @current_feature?
Because I was expecting to use @current_feature together with attribute
like:
attribute(@current_feature, 'my_field')
