Opened 16 years ago
Last modified 14 years ago
#1385 new enhancement
"Field" Support for Print Composer
Reported by: | neumann | Owned by: | mhugent |
---|---|---|---|
Priority: | minor: annoyance | Milestone: | Version 1.7.0 |
Component: | Printing | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | Debian |
Platform Version: | Awaiting user input: | no |
Description (last modified by )
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$
§fieldName§
Change History (3)
comment:1 by , 15 years ago
Component: | Build/Install → Printing |
---|
comment:2 by , 14 years ago
Description: | modified (diff) |
---|---|
Milestone: | Version 1.0.3 → Version 1.6.0 |
comment:3 by , 14 years ago
Note:
See TracTickets
for help on using tickets.
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