Re: Using DSPSIZ keyword

[Booth Martin <booth@xxxxxxxxxxxx>]

Staying with 80 columns is an awful unforced restraint.   We are already 
under a big disadvantage with screen-at-a-time processing.  Willingly 
giving up 50% longer lines to display data strikes me as pain with no gain

 I am not sure what you mean about the resolution changing?  We talking 
font size?  That is a simple setting.


On 4/16/2018 9:00 PM, Lynne Noll wrote:
> I tried 27x132,  but switched back.  The resolution changed.
>
>
> I think the usual emulators can do either, but the configuration has to support the 27x132 to display it without an error.
>
>
>   At my last job, I couldn't depend on people having 27x132 configured, and they'd bomb if  they weren't configured to display it.  In most cases, I coded to 24x80 unless there was a reason to go bigger, and then I'd check if the station allowed 27x132 before opening the display  file.  If it didn't, I'd call a warning window to tell them to get their configuration changed  if they needed this application (a lot of them were engineers who would do it themselves.)
>
>
> For a few things, I coded two different display files (LISTSQL has two because it composes the screen on the fly based on available space) but it is too much overhead for a routine solution.