PureBasic Forums - English

I was using the input() function to halt program execution so I could read output before the console closed. Like this:


OpenConsole()

Input()
End

CloseConsole()


Just hit enter to end the program. Works fine in the IDE. But compile and run the .EXE and instead of closing the program it ...

Yes, thanks. I did find the log in button on the purebasic page. They really should make that more visible. But to be fair that is the standard place to put a log on button. I just wasn't thinking log in.

Yes I was using the AI overview to do fast syntax checking. It is faster and more readable ...

Does redim clear the array?

I ran the following code:

Dim parr(10)
OpenConsole()
For i=0 To 10
parr(i)=i
Next

For i=0 To 10
PrintN(Str(parr(i)))
Next

PrintN("xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx")

ReDim parr(10)
For i=0 To 10
PrintN(Str(parr(i)))
Next
Input()
CloseConsole ...

How do I upgrade to the latest version payed version? I went to the download page but only saw the free versions. I bought a license many years ago.

Currently running version 6.00 Beta 5 (x64).

I'm going to install PB 6.0, learn to use DPI and start over understanding windows and screens.

That's all well and good, but that's not the cause of the problem here. The problem is an IDE tab issue, not a coding issue, because the source code in IDE tab 4 compiles and runs differently to the ...

If you use DPI settings in compiler and DesktopResolutionX(Y) in your code you can use any scaling without changing the Apps size on screen.


Yes, that is probably best coding practice anyway. But the book I was using does not mention it. It is hard to find even in the purebasic documentation ...

We need to know if Paul is running his monitor above the resolution recommended by windows. Or if a different monitor fixes it.


I am running a 4K monitor using what Windows10 is recommending... 3840x2160 at 150% Scale



Ah!! It's the scaling. My scale was at 225%. I changed it to 100% and ...

Windows recommends 1920x1080,... what is the hardware resolution of the monitor, which produces the problem?


That's the thing, its a 65 inch HD tv. It allows me to set the resolution as high as 4096X2960. Under active display settings it tells me I have an active signal resolution of 4096x2960 ...

argggggggggggg what happened. My last post didn't make it for some reason. Maybe I just forgot to press post...

Anyway, I changed my monitor with a 24 inch one with a 2560x1440 resolution and the problem vanished. Its the monitor?!?

I switched back to the big screen at 3840x2160 and it reappeared ...

So far there are two of us who see the problem. The only point of commonality that I see is the 20 series geforce graphics card. If anyone with a 20 series card does not see the problem please speak up. I have no idea how or if a graphics card can cause this but it is the only thing I have.

darius676 wrote: Thu Mar 17, 2022 12:39 pm Do you use DPI settings in the Compiler Options and DesktopResolution when creating the window?

No but even if I did it would give consistent results and not depend on running other tabs or the order That I run the tabs.

I didn't even see a DPI setting in compiler options. Where is that?

I can't get this to look right at all, as shown in the video with the red exploding and then imploding circle, for me it always look broken, the grey and black noise, regardless of tab I'm compiling from.

PureBasic 5.73 LTS (Windows - x64)
AMD Ryzen 5 PRO 4650GE with Radeon Graphics


Maybe you ...

Unless the problem can be identified it isn't going to get fixed. It's not a pb issue


It seems to me that something in the PB IDE must be getting corrupted. Otherwise how do you explain the code working in the first three tabs I run (any first three tabs!) and not working in the fourth tab ...

ok I was going to ask if this this looks ok and reports the correct values for Width and if Resolutions = 1
Try PB6.00 it's only in beta for the c backend the fasm code is stable


ExamineDesktops()
Debug "width " + DesktopWidth(0)
Debug "height " + DesktopHeight(0)
Debug "Res x ...

Three other things to note:

1) I'm using purebasic 5.72. I clicked the check for updates button and nothing happened.

2) Windows recommends I set my desktop to 1920x1080. I have my resolution set to 3840x2160. This has never been a problem for me. The window that opens too large looks about like ...