jdugge
commented
4 years ago As @nyalldawson pointed out in a comment on a pull request:
There's a reason these have been previously omitted -- there's no dependency resolution happening with evaluation of layout properties. So if you attempt to use these variables to move or resize other items then the results will be unpredictable. They'll work or not randomly, based on the order in which the other item's positions are calculated.
I'm personally -1 to including these before we get dependency resolution, as we just won't be able to deliver stable results until then.
Related issues: #26657, #25514
Looks like this needs a significant amount of work, so maybe it's best to remove the "Easy fix" label from this issue.
Author Name: Kepes Ádám (Kepes Ádám) Original Redmine Issue: 17873
Redmine category:map_composer/printing
A seen on the picture, 'item_id' is a variable. That would be very useful to recall another item's position variable (x,y, width, height). This way , in the situation seen on the picture, in the case of two or more attribute tables they could be automatically placed with a query in their position field.