Yeah, i've done it countless times and it's very painful indeed - but the
alternative "losing context" would be even worse to me. Can we do both - i.e. have
the barcode on the screen alongside the oops itself? (although at that point they'll
be taking screen real estate from each other - degrading the information in *both*
venues.)
Keyboard 'oops scrolling' driver with 'flip to barcode output' key? :-)
If we can make the screen scroll, or guarantee that a hot key will switch to
the barcode view, then those look like good solutions. Sharing space on a
non-scrollable view sounds like a poor choice. Perhaps better to have a
command line option to say which to provide (default = text).
-Tony