When you run a program from within IT using F7, the menu Debug >> Debug current program, or the menu option Run >> PxPlus the system will spawn a new instance of PxPlus using the default window size.  The default consists of an 80x25 window inside a window frame container whose dimensions is set in your INI file in the [WindowFrame] section.

Generally I suggest that you override these by providing a START_UP program that sets whatever you want as a minimum window size by calling *cmd/system/wdw and passing the size desired as WWxHH (e.g. "100x30").  This will create the base window the size desired, however you will still need to adjust the outer frame size to suit your needs.

You could also try adding the following commands to your START_UP:

CALL "*cmd/system/wdw", "100x30"  ! Or whatever your desired minimum cols/lines might be
CALL "*cmd/system/wdw", "zoom auto"

This will tell the system to create a 100x30 window then adjust the font size so you end up with the desired window size (in terms of columns/lines) within the frame and to tweak the frame size to match the window size.  The auto option enables tracking any frame size adjustments made by the user and have the system adjust the font accordingly.

To see what you have open, on Windows click on the icon in the upper left (or press ALT-SPACE) then select About PxPlus.  From there select the info button.  This will show you all files, windows, controls and object you are using.

Also, to avoid unwanted left over objects, always consider adding a FOR clause when creating an object with the NEW function which will allow you set dependencies on the new object which will allow for automatic deletion.  For example if the object is only used in a subroutine while its active you could add FOR PROGRAM.

Oh and if you really want to use a single line input and have access to 'SelectOffset, 'SelectLength, etc., use a POPUP menu on the control.

Windows will NOT clear the selection if you right click to invoke the popup menu for the control so in your popup menu logic you can access the selection information.

This is how Windows handles this -- Anything looking to access the selected text generally does so from a Right click popup especially when dealing with single line input fields.

There is a limit as to the number of lines high a window can occupy.  These limits changed in PxPlus 2021.  What version are you running?

You probably should review Regular Expressions ..

Basically for what you want would be

DIM.*MYVAR

Here is a link to more details about regular expressions which are used by the MSK function:
https://manual.pvxplus.com/page/functions/msk.htm

You can find more information about using zip files with PxPlus at

https://manual.pvxplus.com/page/PxPlus%20User%20Guide/File%20Handling/Processing%20Data%20Files/Accessing%20ZIP%20Files.htm

Support for Zip files was added in 2014.

It likely would be easier to just use Pseudo control handles.  You can use the *system object to get the handle for any control in the system and then use it anywhere to access the control. 

https://manual.pvxplus.com/page/objctl2/overview.htm

->button 10,@(10,10,10,10)="hello
->osys=new("*system")
->%Btn_handle=osys'Control(10)
->?Btn_handle
 1000100010

There are two types of errors you could received from this utility.

• The first would be an expected error such as a password failure, invalid table name, etc.  These will be reported in the error message which will be NULL if no error occurred, non-null indicates an error.
• The second would be a totally unexpected error such as file corruption or IO error.  These can be caught using an ERR= option.

Checking ERR would only be appropriate if an ERR= branch was taken.