how?
yeah! also
depends on whether you want them to press a specific key or not...
if you want them to be able to press Any key:
Do
Print "some random crap"
Loop until inkey$ <> ""
also, to have them use ESC key:
Loop until inkey$ = chr$(27)
if you want them to be able to press Any key:
Do
Print "some random crap"
Loop until inkey$ <> ""
also, to have them use ESC key:
Loop until inkey$ = chr$(27)
- {Nathan}
- Veteran
- Posts: 1169
- Joined: Thu Aug 19, 2004 6:08 pm
- Location: The wetlands of central Ohio, USA
- Contact:
I will explain it (and guys, use the code tag!)
Just thought you should understand it. I refused to do soooo many things because I didn't understand it. I hated it when Vic said just "to put &h3da, 0 in your code. Just do it." without an exclamation!!!
Code: Select all
do 'duh, starts the loop
DOYOURLOOPCRAP 'psuedo code
loop until inkey$ = Chr$(Scancode)
'the line above loops the loop until the a key keyboard buffer
'(retrived by inkey$) is equal to a certain scancode. Then, if it is,
'it stops the loop. You can also use "loop until inkey$ <> "" because
'if no key is in the keyboard buffer, then it returns a null (nothing)
Look up PLAY in the help index.
No, you cant do 3d. No, you cant play mp3s or wav. No you cant do multiplayer over the internet. No you cant write an OS.
What else.. Nope, I think that covers it.
By the way, the whole idea of a forum is that you post, and wait, usually a few days. This is not a chatroom.
No, you cant do 3d. No, you cant play mp3s or wav. No you cant do multiplayer over the internet. No you cant write an OS.
What else.. Nope, I think that covers it.
By the way, the whole idea of a forum is that you post, and wait, usually a few days. This is not a chatroom.
I have left this dump.
Yes, you "can" do 3D in QB.. but YOU can't (And neither can I for that matter)
Moving on:
Spelling, learn it, use it. Dat is sum good shitz u no!
And on:
www.freebasic.net
Further down the line now:
No, QB is unable to multitask in any way. You can fake that by quickly switching between actions. Using a loop is very common, then determine what to do and when either by user input or using fixed algorithms.
Multiple variables, or even arrays are also good to know about.
Are you a troll?
Moving on:
Spelling, learn it, use it. Dat is sum good shitz u no!
And on:
www.freebasic.net
Further down the line now:
No, QB is unable to multitask in any way. You can fake that by quickly switching between actions. Using a loop is very common, then determine what to do and when either by user input or using fixed algorithms.
Multiple variables, or even arrays are also good to know about.
Are you a troll?
I have left this dump.
-
- Veteran
- Posts: 703
- Joined: Sun Nov 14, 2004 7:36 am
- Contact:
Its atleast 95% equivalent to QB....the main thing is anything that is 16 bit related is no more being it's a 32 bits language now. hence no memory problems, no DEF SEG statement, it has inline assembly which is a bit better code wise if you need it . but remember that it's 32bit assembler, not 16 bits .
It has many more SCREEN modes and parameters, integrated mouse support...in short, you don't really have a good reason to stay with QB today.
It has many more SCREEN modes and parameters, integrated mouse support...in short, you don't really have a good reason to stay with QB today.
When God created light, so too was born, the first Shadow!
MystikShadows
Need hosting? http://www.jc-hosting.net
Interested in Text & ASCII development? Look no further!
http://www.ascii-world.com
MystikShadows
Need hosting? http://www.jc-hosting.net
Interested in Text & ASCII development? Look no further!
http://www.ascii-world.com
-
- Veteran
- Posts: 1055
- Joined: Sun Jan 02, 2005 2:11 pm
- Location: At my computer
- Contact:
Um... 99%.... Its only a few things that FB doesn't do that QB does, but what more FB does makes up for it.....
btw, FBC alone is a commandline compiler, to start off you might like a IDE:
http://fbide.sourceforge.net/
The FBIde + FBC 0.14b is the best choice.... gives you the whole nine yards....
Also, help on FreeBASIC commands is here:
http://www.freebasic.net/wiki/wikka.php?wakka=FBWiki
You should find that is very much like QB..
Also.. basicaly QB is 16bit and has issues with newer 32bit computers,... making FreeBasic compiling at 32bit better... ... As for what it totaly means, I don't keep up with.... just which is better...
btw, FBC alone is a commandline compiler, to start off you might like a IDE:
http://fbide.sourceforge.net/
The FBIde + FBC 0.14b is the best choice.... gives you the whole nine yards....
Also, help on FreeBASIC commands is here:
http://www.freebasic.net/wiki/wikka.php?wakka=FBWiki
You should find that is very much like QB..
Also.. basicaly QB is 16bit and has issues with newer 32bit computers,... making FreeBasic compiling at 32bit better... ... As for what it totaly means, I don't keep up with.... just which is better...
-Kevin (aka:Rattra)
(x.t.r.GRAPHICS)
(x.t.r.GRAPHICS)
- The Awakened
- Veteran
- Posts: 144
- Joined: Sun Aug 07, 2005 1:51 am
http://petesqbsite.com/sections/tutoria ... ycodes.txt
You CAN look this stuff up on the website before you come here.
You CAN look this stuff up on the website before you come here.
"Sorry for beating you up with a baseball bat Julian, but I DID think that you were a samsquanch."
In answer to bits:
Well, when I was back in school, only 3 year ago, anywayz, we still learned about bits and bytes.
But to cut to the chase... 16 bit... if you know MS-DOS, that's 16 bit. 16 bit is some kind of boundry. Until we got windows 95 (I believe we actually got it before with WIndows NT) we were introduced to a new boundry, the 32 bit. This standard worked a couple of years, until we noticed we needed to cross the boundry again, giving us: tada: 64 bit. Just for the record: 32-bit works just fine.
Just for the record: the bits in this case have nothing to do with the bits, bytes, kbytes, mbytes, gbytes of the RAM memory or Harddrives etc.
Grtz
Seb
Well, when I was back in school, only 3 year ago, anywayz, we still learned about bits and bytes.
But to cut to the chase... 16 bit... if you know MS-DOS, that's 16 bit. 16 bit is some kind of boundry. Until we got windows 95 (I believe we actually got it before with WIndows NT) we were introduced to a new boundry, the 32 bit. This standard worked a couple of years, until we noticed we needed to cross the boundry again, giving us: tada: 64 bit. Just for the record: 32-bit works just fine.
Just for the record: the bits in this case have nothing to do with the bits, bytes, kbytes, mbytes, gbytes of the RAM memory or Harddrives etc.
Grtz
Seb