With LINE INPUT you'll read a full line at once.

Looking at it, it looks like LINE INPUT just reads the file line to a string variable, so to get the values out of it I'm back to trying to parse a string. I guess I could read the line from the file, PUT that line to a temporary file, and then read that with INPUT? That doesn't seem much more efficient than what I'm already doing. But maybe I'm missing something.

OK so maybe I'm misunderstanding the use of C libraries in QB64. Is it that QB64 has support for certain C libraries, or they are already built in?

I found an XML library consisting of a ".c" and a ".h" file. I tried putting "DECLARE LIBRARY ".\xml_parse_lib"" into a test program and QB64 actually crashed on me every time I tried to do it. Is this a bug, something I did wrong, or is it just that this is something QB64 isn't supposed to do? You would think the program would just flag it and say "nope, can't do that" instead of crashing though.

Guess I need to find another method. XML is convenient but it certainly isn't the only way to do things. I was just hoping not to have to write something to parse strings myself, so that I can actually worry about programming a game. Oh well.

EDIT: So I did some more reading and discovered the use of OPEN and INPUT for reading files, so I can do basically what I wanted to do with the XML as comma-separated files instead. Gosh, I keep answering my own questions.

XML would still be nice as an intuitive way for a human to read the file. But not critical for what I'm doing right now.

Take a look at Task 9 in my tutorial: http://qb64sourcecode.com/Task9.html

I go over each method of keyboard input along with example programs to accompany them.

_KEYHIT has many of the same limitations as the INKEY$ command mainly being the buffered input and slow repeat rate. Not really great for games that need instant keyboard response. In order to implement _KEYHIT for fast action games you'll need to create a latching variable and then detect when the key has been released which _KEYHIT can do as well.

I'll have to give this a closer look! Funny, I actually had found your tutorial before I joined this forum and it was already open in a tab in my browser, I just hadn't read through it fully yet!

_KEYDOWN seems to definitely be working for my purposes. I changed the code so that you can use A and D for movement with RCTRL for jump and it works fine. Something about those keys with Shift seems to be funky on this keyboard, for sure.

Thanks all for the welcomes, and for the helpful links. I'm enjoying writing programs with QB64 so far, so hopefully I can be a helpful participant on the forum. QBASIC was my first exposure to programming back when I was around 10 years old, which was...*looks at watch* 26 years ago now. Wow I feel old. But because of that I was extremely excited to find out QB64 was a thing.

Hello all, I'm new so I'm sorry to bug you guys with a question in my first post, though I'm sure that happens a lot. I'm also sorry if this has been brought up before but I wasn't able to turn anything up on the Google.

I'm trying to use the _KEYDOWN function for input to a game. Specifically I'm trying to use the A and D keys to move left and right, and the right shift key to jump. However, for moving right, for example, I'm using "_KEYDOWN(68) OR _KEYDOWN(100)" so that the player still will move even if the user leaves CAPS LOCK turned on or if the player is trying to move and jump at the same time. Like so:


The problem is that the A or D key will "stick", that is if I'm jumping and moving right, and release the D key before releasing Shift, the game thinks the D key is still pressed and the player continues moving to the right until the D key is pressed and released again.

My first thought was this had to be a bug with the _KEYDOWN function but being that I'm new to QB64 it's more likely an error on my part, that I'm somehow not using the function properly. Can anyone help me shed some light on this? Thank you in advance for your help!