!!! I found it !!!!

So the problem is that I have a number of variables for which I perform a ReDim but I never have an original DIM statement.

In my code, this works just fine, but apparently Debug does not like this.

I simply placed a "Dim PartitionSize(0) as String" near the start of my code with all the other DIM statements and the problem is solved.

The problem is that I think I do this with a bunch of variables so I need to look at every single ReDim in my 13,000 lines.

So, the logical question: Should what I am doing (ReDim without a preceeding Dim) ne valid or not?

Pete, that actually made it worse. It gives me a subscript out of range right on the line where the breakpoint was set.

That is actually a recurring theme now. If I do not set a breakpoint, no error. The code runs fine.

If I set a breakpoint where I noted in my repro, then it fails a few lines later at the line that reads "TotalPartitions = 0 ".

If I set a breakpoint AFTER that line, the code will run fine up until that breakpoint but immediately fail when it hits that breakpoint.

So it seems to me that the line "TotalPartitions = 0 " is a key to this, BUT, it only causes a subscript out of range when in debug mode by stepping to it with F7 or by setting a breakpoint on or after that line.

Okay, hold off looking at this. I think I found my problem. Just wanted to shout before I wasted more of your time. I should have confirmation in a couple minutes.

Thank you. I appreciate you taking an interest in this.

Running build 1e67962 on Windows 11.

I'll attach the code as a ZIP file! Fortunately, because I'm focusing on a new section of code I put in some test code to simply bypass huge chunks of code and take me to the portion that is my current focus so really very little code is run at this point.

The code has to run elevated, so to make that work with QB64, I have run QB64 as admin.

Here are the steps to repro:

Set a breakpoint on line 3883. This line reads: If Temp$ = "H" Then

Run the program (F5). Make sure that QB64 is being run elevated.

On your system, you may get a warning that the Windows ADK is not installed (not sure if you will or if I am bypassing that section). The program requires this for some operations but for this test it won't matter. Just continue if you do get such a warning.

You will get just a few questions before the breakpoint. Here are the answers and responses to supply:


Q: For this project, should we exclude the autounattend.xml answer file if it exists?
A: Y

Q: Do you want to inject an EI.CFG file into your final image?
A: Y

Q: Single, Multiple, or Help: ?
A: M

You are now at the breakpoint. Press F7 a few times. You only need to go as far as the line of code that reads

TotalPartitions = 0

Go a line or two past that and note that all is well.

Stop the program.

Set a watch for "PartitionSize" specifying indices 1-2.

Perform the exact same steps as above. As soon as you hit the "TotalPartition = 0" you should get a subscript out of range.

  [ You are not allowed to view this attachment ]  

Pete, sorry, missed your post initially. Actually, it is when clicking the maximize button that the problem happens. It does not happen when dragging the corners as was suggested.

I've always just sort of lived with this but I thought that I would inquire to see if there was any sort of setting somewhere that can affect this.

I notice that in the IDE the item selected or highlighted is well below the position of the mouse pointer. Take a look at the screenshot below. You can clearly see that the mouse pointer is on the line for "Save" but the IDE thinks that I am pointing to "Save As...".

Any kind of setting to tweak this behavior?

  [ You are not allowed to view this attachment ]  

I wrote a program that performs a LOT of operations by running Windows command line utilities via SHELL commands. Because of this, I have simply been doing many basic file operations like copying and moving files using SHELL commands along with Windows COPY, MOVE, ROBOCOPY, etc.

However, it just seemed odd to me lately that I'm not seeing equivalent commands for these simple operations in QB64. It's entirely possible that I'm simply missing something. Could someone just tell me if I'm being obtuse here or is running commands like COPY, MOVE, etc. via SHELL the normal way to perform these operations?

Sorry, I already had one idea today that I posted earlier, but here is another.

There are times when I open 2 QB64 Windows side by side so that I can compare some existing code from one Window and start making modifications to a copy of the file in the other window. However, there are times where I accidentally started doing code updates in the wrong window. It would be great if there was a toggle to make one window a view only window. That way, if I started trying to type into the wrong window and saw that nothing was happening (or maybe even a beep could play), I would have instant visual feedback that this is my view only window.