Open DelazJ opened 3 years ago
I would guess that simply doing context.appendScope
to the context made here https://github.com/qgis/QGIS/blob/8eb1a45e219c480bb78affb3ee797f9e7b47a6bc/src/gui/qgsexpressionselectiondialog.cpp#L58
with a scope made with a nullptr like https://github.com/qgis/QGIS/blob/072222d2fd4850f1ae73a58817ccfd22b6c5dfda/src/gui/symbology/qgssymbolwidgetcontext.cpp#L97 would do the trick.
I think this is more of a feature request than a bug judging from the code.
100% feature request and potentially unstable anyway. This will never occur in a layout and this will never have a definite atlas and may cause strange behaviour in some cases. Which is not the case for rendering.
I don't know whether it has been available in the past or not, so feel free to turn it into feature request depending on the status.
It's not possible to refer to atlas feature properties when using the selection tool. But i can imagine contexts where someone would like to select features in a layer based on whether they share (or not) common attributes or some spatial relationship with the atlas feature.
left (the select by expression tool) right (the expression dialog from symbology) - same layer