You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many conventions provide a sticker for program participants to attach to the back of their member badge. While it's possible to export the data and generate badges in external software, having a Zambia report to produce labels directly would simplify the process significantly.
The report should allow formatting for different label sizes, and print without Zambia page headers, all which can be achieved with CSS.
The text was updated successfully, but these errors were encountered:
I have developed a new report for printing program participant labels.
It lays out the labels in printer units (selectable in cm, mm, or inches) with CSS formatting.
It provides a form for customising the label size and font size, and selecting badges to print:
The form fields are handled by javascript handlers, so label size changes are displayed in real time.
Headers, footers and form elements are hidden when printing by @media CSS selectors, so only the labels are printed.
The form also allows a list of member IDs to be specified (e.g. A0004, A0050-A0059, M1001), and only specified members will be printed.
It also allows blank labels to be added to the start, to allow partially used label sheets to be reused.
Finally it can add a border to the labels, which can be useful for checking positioning, but probably isn't wanted in the final print run.
Here's a preview of the printed label page (with borders on):
Many conventions provide a sticker for program participants to attach to the back of their member badge. While it's possible to export the data and generate badges in external software, having a Zambia report to produce labels directly would simplify the process significantly.
The report should allow formatting for different label sizes, and print without Zambia page headers, all which can be achieved with CSS.
The text was updated successfully, but these errors were encountered: