01-11-2023, 09:28 PM
(This post was last modified: 01-11-2023, 09:29 PM by Kernelpanic.)
Quote:SMcNeill - From the error message that you're reporting, you're basically getting a "Locate out of bounds" type glitch. Why are you getting it on the second run and not the first?? I dunno! Maybe windows has some sort of setting where it tracks width and height of a console on a per instance ran.
Like mnrvovrfc mentioned, I think the problem will go away as long as you specify the size of the screen yourself. Add a simple line WIDTH 120, 30 at the top of your code, under the $CONSOLE:ONLY, and I don't think you'll have any issues anymore.
No change! It is as already described, once it works, then you only see the command line flashing briefly, but it doesn't stay. In this context, I noticed this flashing or a short flickering in all tested programs under 3.5.0, and only then does the command line appear. Only with the Vattenfall program does it not appear. I have now tested everything I could think of, I can not find an explanation for the behavior.
As a speculation I can think of, maybe this version does not get along with the long variable names. Pretty fantastic, but I have found over the years that there is no bug that does not exist!
To reiterate, with 3.4.1 this issue does not exist.
Same behavior.
Code: (Select All)
$Console:Only
Width 120, 30
Option _Explicit
. . .
'Fuer Press Key . . .
'Locate 27, 0
End
That is how it goes: No Console, and no Locate in row 67
Code: (Select All)
'$Console:Only
'Width 120, 30
Option _Explicit
. . .
'Fuer Press Key . . .
'Locate 27, 0
End
The Locate on line 67 has only this purpose: