The priniple of an accumulating variable and re-drawing the screen is fine until I consider the memory overhead. Additionally the buffer for the console is seldom up to the sizes we are thinking of. The use of repeated MODE commands to re-size to best fit Output is a very SLOW process. Each MODE on my W7x64 Workstation can add 2 seconds to the execution as it spawns a shell etc. I have also notice, which is another gripe, that if I Maximize a console which has not had a MODE applied to it, it will maintain the pre-defined width = Usually 80 chrs, and will do full height on the default screen size. If however I have applied a MODE to it, SetConsole("Maximize") has no effect at all as I have already specified 'MY' size.
What I think has potential is the DPI and similar registry entries. I need to collate a bank of information covering XP to Win7 64 which will give me DPI, Default FONT etc... I still however have no idea other than MODE whether I can script a change to the size and font size of a console in use ! It SHOULD be possible as in the GUI it is possible to change the chosen console using (Right Click) Context Menu, Properties !
|