-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Field" Support for Print Composer #11445
Comments
Author Name: Andreas Neumann (@andreasneumann) parts of it (currenDate) is already implemented in print composer. This was also the most urgent one of the proposed fields. I still think that other fields should be added later on, but it is ok to move this to 1.6 |
Author Name: Alister Hood (@AlisterH)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Alister Hood (@AlisterH)
I think these would be useful:
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Pirmin Kalberer (Pirmin Kalberer)
|
Author Name: Andreas Neumann (@andreasneumann) This is implemented as part of the Atlas plugin. It allows to use the expression builder for any label element in print composer. People may want additional expressions, but they should go into the expression builder.
|
Author Name: Andreas Neumann (@andreasneumann)
Original Redmine Issue: 1385
Assignee: Marco Hugentobler
It would be useful to have "field" support in the print composer. Fields are variables and would be part of text labels in the print composer. The field value/content would be replaced when printing/previewing the map layout. Fields are common in text-processing.
Potential candidates for fields are:
current date, proposed fieldname: currentDate
current username (on an operating system level), proposed fieldname: currentUser
current project title, proposed fieldname: currentProjectTitle
current projection, proposed fieldname: currentProjection
current map units, proposed fieldname: currentMapUnits
Are there more useful field names in this context?
There would have to be delimiters who separate fieldnames from regular text, potential formats:
§fieldName§
The text was updated successfully, but these errors were encountered: