If you have a simple program where you only want to show the contents of one screen like this
PRINT " 1 ", 10, 100
SHOWSCREEN
MOUSEWAIT
there is no output displayed. To see the display you need to add an additional SHOWSCREEN which shouldn't be necessary like this -
SHOWSCREEN
PRINT " 1 ", 10, 100
SHOWSCREEN
MOUSEWAIT
First example works fine for me with default settings in a new project.
It does for me too...
Hmm.... I've created a brand new project and now it's working fine. Maybe it's something from a previous run of a program. I'll see if I can work out how to reproduce it.
Thanks all for testing!
Okay, I've figured out how to reproduce the bug.
Create a project
Code as follows
print "1",0,0
showscreen
mousewait
If you test that you'll get "1" printed on the screen.
Turn debugmode on and run it again.
Where has the output gone?
Still works fine for me, with or without debug mode.
FC are you using a mac with glbasic?
Gaaaaaaaaaaaaa!!!!!!! :rant:
It breaks here, not sure why it's working for everyone else - this is very frustrating!!!
Hemlos : I'm running 7.141 on win XP SP3
Drivers issue mabe?
Can one of you please try my project file then?
I created the project in c:\zzz, i've attached the project and source files.
Try it first without debug, then with debug.
[attachment deleted by admin]
I tried it, works ok for me,
i wonder if the compiled version from my computer will make it act right on yours? (attached to this message)
FC download this file and run it..
And ...GLBasic IDE, Version: 7.144
[attachment deleted by admin]
Thanks for testing Hemlos.
I tried your exe and I get the "1" output.
I then tried my compiled exe and I get the "1" output there too.
It only happens within the IDE in debug mode. Very strange...
I'll update the IDE to 7.144, not that I expect any change - as Moru suggested it's probably the graphics drivers on this PC. It's not my regular PC and I don't have any control over the drivers so I can't update them to the latest (assuming they're not the latest version). Also, it's an integrated graphics card so it's not going to be overly sophisticated anyway.
Oh well, unless Gernot sees this and has any suggestions, we'll assume it's a graphics driver issue.
Thanks for your efforts Hemlos/Moru/MrTAToad! It's an awesome community as always!!!
do you have such a problem on a real project?
No, I noticed it when I was doing some short programs to figure out some commands. The main reason I raised it as a bug is that I wouldn't want someone new to GLBasic to try a "Hello World" type program and get worried because it didn't work.
The problem goes away after the second SHOWSCREEN so in a game the problem will be gone after the first 1/60th of a second.