Skip to content
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

Closed
qgib opened this issue Nov 6, 2008 · 7 comments
Closed

"Field" Support for Print Composer #11445

qgib opened this issue Nov 6, 2008 · 7 comments

Comments

@qgib
Copy link
Contributor

qgib commented Nov 6, 2008

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$

§fieldName§

@qgib
Copy link
Contributor Author

qgib commented Jun 13, 2010

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

@qgib
Copy link
Contributor Author

qgib commented Jul 18, 2011

Author Name: Alister Hood (@AlisterH)


Are there more useful field names in this context?

  • File name (and path)
  • Composer layout name
  • Scale (when there is more than one map in a layout there would need to be a way to tell it which map to get the information from)

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.0 to Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2012

Author Name: Alister Hood (@AlisterH)


Are there more useful field names in this context?

I think these would be useful:

  • saveDate - the date the project was last saved
  • layerSaveDate - the date a particular layer was last saved.

  • pull_request_patch_supplied was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Apr 15, 2012

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.4 to Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2012

Author Name: Pirmin Kalberer (Pirmin Kalberer)


  • fixed_version_id was changed from Version 2.0.0 to Future Release - Nice to have

@qgib
Copy link
Contributor Author

qgib commented Oct 6, 2012

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.


  • status_id was changed from Open to Closed

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant