<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Verdana",sans-serif;
font-variant:normal !important;
color:#1F4E79;
text-transform:none;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'>Martin, Andreas, Nyall,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'>thanks again for your answers and your help. This list ist really great, you not only get answers very fast but you can even be informed about the backgrounds. Fantastic! The software support for expensive GIS Software is very often far away from that level.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'>My idea to the question of circular refs: objects in print composer, e. g. rectangles and triangles, must have some kind of information about their position relative to other objects on the same level. They know if they have to draw on top or below of others.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'>In styles dialog (outside print composer), the drawing order for streets, rivers and so on can be chosen by setting symbol levels.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'>Maybe one of those mechanisms can be used to teach a composer object from which other objects on the same hierarchy level it can read variables and from which not? Just an idea.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79'>Mit freundlichen Grüßen,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;font-variant:small-caps;color:#1F4E79'>Uwe Fischer<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Verdana",sans-serif;color:#1F4E79;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Von:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Nyall Dawson [mailto:nyall.dawson@gmail.com] <br><b>Gesendet:</b> Donnerstag, 23. Juni 2016 23:24<br><b>An:</b> Andreas Neumann <a.neumann@carto.net><br><b>Cc:</b> qgis-user <qgis-user@lists.osgeo.org>; Uwe Fischer <gisfisch@t-online.de><br><b>Betreff:</b> Re: [Qgis-user] Variables in print composer<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p>On 23 Jun 2016 21:57, "Neumann, Andreas" <<a href="mailto:a.neumann@carto.net">a.neumann@carto.net</a>> wrote:<br>><br>> Hi Uwe,<br>><br>> All "map_xx" variables are only available on the map frame item itself (when it is selected) - nowhere else. Items in print composer are on the same hierarchy - so can't see each other's scope or variables in each scope. But all items in a composition can see the "composition" variables because they are one hierarchy above in the scope.<br>><br>> That's a limitation you can't currently overcome. It would be nice to cross-reference variables from other elements in the same hierarchy - but it is not possible currently - at least I don't know how.<o:p></o:p></p><p>Andreas has summed it up perfectly. I originally had a function which allowed items to access variables from another composer item, but had to pull it out as it opened the risk of circular references (ie data defined position for an item which uses item position variable from another item, which in turn uses a variable from the first item). It's not trivial (or fun) to solve, but if sponsorship is available I could fix this.<o:p></o:p></p><p>Nyall<o:p></o:p></p><p>><br>> Andreas<br>><br>> On 2016-06-23 13:36, Uwe Fischer wrote:<br>>><br>>> Martin,<br>>><br>>> <br>>><br>>> thank you very much for your tip, but in the variables list no variables of type „map" show up (please see attachment). But in print composter they are present and visible.<br>>><br>>> <br>>><br>>> Mit freundlichen Grüßen,<br>>><br>>> <br>>><br>>> Uwe Fischer<br>>><br>>> <br>>><br>>> Von: Qgis-user [mailto:<a href="mailto:qgis-user-bounces@lists.osgeo.org">qgis-user-bounces@lists.osgeo.org</a>] Im Auftrag von Martin Stubbs<br>>> Gesendet: Donnerstag, 23. Juni 2016 12:46<br>>> An: <a href="mailto:qgis-user@lists.osgeo.org">qgis-user@lists.osgeo.org</a><br>>> Betreff: Re: [Qgis-user] Variables in print composer<br>>><br>>> <br>>><br>>> On 23/06/16 08:30, Uwe Fischer wrote:<br>>>><br>>>> Hello List,<br>>>><br>>>> <br>>>><br>>>> what is the use of variables in print composer? A map frame has variables assigned like map_extent_height and _width. But how to make use of those variables? If I try to place a rectangle around the map frame using the determined extent variables (plus something), I cannot use the variables. There is a ‚data defined override' section in the Position and size dialog for rectangles, but when I select ‚variable' it tells me that there are no variables, which seems to be nonsense.<br>>>><br>>>> <br>>>><br>>>> <br>>>><br>>>> Best regards, Uwe<br>>>><br>>>> <br>>><br>>> Uwe,<br>>><br>>> When you select a Data_defined_override in Position and size, pick edit from the list instead of variable. In the Expression string builder you will find map_extent_height in the Variables list.<br>>><br>>> Regards<br>>> Martin<br>>><br>>><br>>> _______________________________________________<br>>> Qgis-user mailing list<br>>> <a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br>>> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>>> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>><br>> <br>><br>> <br>><br>> _______________________________________________<br>> Qgis-user mailing list<br>> <a href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br>> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><o:p></o:p></p></div></body></html>