Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Tip: full-screen session on Windows

    Using ProTop
    2
    6
    3136
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Rob Fitzpatrick
      Rob Fitzpatrick last edited by

      Are you trying to run ProTop in a maximized proenv session?
      Does it keep resizing on you to 160 x 48, no matter what you do with the Layout tab in proenv Properties?
      Have you pulled out most of your hair?

      Me too! 🙂

      Here's the tip:

      • Edit <protop>\bin\protop.bat and <protop>\bin\protopenv.bat
      • Comment out this line in each: mode con cols=%COLS% lines=%ROWS%
      • Sweep up your hair.

      Happy monitoring!

      1 Reply Last reply Reply Quote 1
      • tom
        tom administrators last edited by

        Great tip Rob!

        1 Reply Last reply Reply Quote 0
        • tom
          tom administrators last edited by

          If I were a better BAT programmer I'd probably modify those scripts to only change the window size if it is too small. But the logic to figure that out eludes me.

          1 Reply Last reply Reply Quote 0
          • Rob Fitzpatrick
            Rob Fitzpatrick last edited by

            Would these ConsoleAPI functions help?

            GetLargestConsoleWindowSize function
            Retrieves the size of the largest possible console window, based on the current font and the size of the display.
            https://docs.microsoft.com/en-us/windows/console/getlargestconsolewindowsize

            SetConsoleWindowInfo function
            Sets the current size and position of a console screen buffer's window.
            https://docs.microsoft.com/en-us/windows/console/setconsolewindowinfo

            1 Reply Last reply Reply Quote 0
            • tom
              tom administrators last edited by

              Off hand that sounds like a whole lot of windows gobbledy gook that probably isn't BAT file friendly...

              1 Reply Last reply Reply Quote 0
              • Rob Fitzpatrick
                Rob Fitzpatrick last edited by

                It isn't batch-friendly directly. But a .bat can also invoke _progres.exe and run ABL, which can declare Windows functions as external procedures, so it might be possible to make it work.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post