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
Send printer configuration commands on print (width/height etc)
Flesh out printing more to allow highly customisable labels (big - possibly use reports or something similar. Possibly plugins. Perhaps both, with plugins for wild cases. Need to refine requirements in PRD, as few specs/details are truly recorded yet.)
In theory, we should absolutely have a default config for our standard labels of ~70x35mm (which is what the current labels assume). But we should be able to adapt that.
Scaling based on amount of directions
Overflow text to multiple labels
Allow printing labels for every line (OG allows even adding multiple lines of the same stock line!), we currently group by item and print one (much pharmacist debate over what is best practice here!)
Allow printing multiple labels for same line with indication of how many packs e.g. 2 labels, with some indication of 1/2, 2/2.
Support warnings. OG only supports printing one warning. Should potentially include ALL warnings for an item, dynamic font size + overflow to multiple labels if needed...
Multiple part labels. OG supports 3 part out of the box, but in the wider world this can be as much as 6 parts, the sky is the limit perhaps.
Some parameters (similar to reports) that allow some configurability such as for above things perhaps, or many different templates to select as default.
Whatever default label config we have should probably be duplicated with the Epson printing language ESC, or we create some abstraction over the two languages in rust... wouldn't be using tera templates in that case though (unless we inject rust funcs and do everything calling those funcs instead... at which point 🤷 )
The text was updated successfully, but these errors were encountered:
Building upon the first epic #6340, we should:
The text was updated successfully, but these errors were encountered: