On 20 June 2014 15:43, Martin Dobias wonder...@gmail.com wrote:
Actually the dot syntax would imply on the fly evaluation. When
parsing, it is not possible to decide what will be the content of an
object.
This would be similar to python: the expression x.y means that in
object x it should
On Fri, Jun 20, 2014 at 1:00 PM, Nyall Dawson nyall.daw...@gmail.com wrote:
On 20 June 2014 15:43, Martin Dobias wonder...@gmail.com wrote:
Actually the dot syntax would imply on the fly evaluation. When
parsing, it is not possible to decide what will be the content of an
object.
This
On 19/06/2014 11:56 pm, Andreas Neumann a.neum...@carto.net wrote:
Hi,
Question: is it already possible to get access to any attribute in the
current atlas feature record?
Hi Andreas,
I've been working on this. I nearly had it ready for 2.4, but in the
end I wasn't comfortable pushing it
Hey Nyall,
I would like to revisit this with you at some stage and maybe explore the
expression context stuff. Having one global variable for all this isn't
going to scale if we ever allow bulk atlas export.
- Nathan
On Fri, Jun 20, 2014 at 1:34 PM, Nyall Dawson nyall.daw...@gmail.com
wrote:
Hi Nyall,
Cool that you had a look at this already. It would open up a lot of
possibilities.
Along the same lines I noticed that the table in print composer is not
updated correctly when iterating in the atlas preview mode (don't know
if it works when generating the pdfs).
My usage scenario was
Hi Nyall
On Fri, Jun 20, 2014 at 10:34 AM, Nyall Dawson nyall.daw...@gmail.com wrote:
What I've done is:
- Add an $atlasfeature variable, which returns the current atlas feature
- Add a $currentfeature variable, which returns the current feature
which is being evaluated (unfortunately
On 20 June 2014 15:18, Martin Dobias wonder...@gmail.com wrote:
May I suggest an alternative approach: to introduce dot notation, e.g.
$atlasfeature.area_code - that looks much more like SQL syntax and it
is easier to remember and use. It would require small adjustments to
the parser and
On 20 June 2014 15:07, Andreas Neumann a.neum...@carto.net wrote:
Hi Nyall,
Cool that you had a look at this already. It would open up a lot of
possibilities.
Along the same lines I noticed that the table in print composer is not
updated correctly when iterating in the atlas preview mode
On Fri, Jun 20, 2014 at 12:29 PM, Nyall Dawson nyall.daw...@gmail.com wrote:
On 20 June 2014 15:18, Martin Dobias wonder...@gmail.com wrote:
May I suggest an alternative approach: to introduce dot notation, e.g.
$atlasfeature.area_code - that looks much more like SQL syntax and it
is easier
