Qbasicnews.com

And your statement is still not true...the relative path in your example is the default directory, since there is no path.

You might want to check your facts.

A bat file makes you go into the directory of the bas file it is running.

So you're telling me that you can change the default directory with a batch file...congratulations, you've passed level 1 of DOS competency. Now tell me, what does this have to do with "relative paths not working"?

Not using relative paths makes your game not desirable to install. If I have to install something in a fixed location I don't install it 'cause I have my own HDD distribution.

I really can't see a single situation where relative paths don't work for fetching your datafiles.

The direct link to my article: http://faq.qbasicnews.com/?blast=RelativePaths

Quote:So you're telling me that you can change the default directory with a batch file...congratulations, you've passed level 1 of DOS competency. Now tell me, what does this have to do with "relative paths not working"?

Quote:I really can't see a single situation where relative paths don't work for fetching your datafiles.

Why do I have to repeat myself?

Relative paths don't work unless you're using a bat file or you have already compiled your program. . .

I dunno. I just go to DOS, change to the directory of my game, whatever it is, and QB.EXE is in the PATH system variable, so... I run QB from the directory of the concrete game I am coding, and the BAS file (uncompiled) finds the data files.

What I really don't understand is why people is coding for a DOS compiler if they can't use DOS properly. Running QB in a window is bad policy, using the windows explorer to run QB and/or BAS files is bad policy. That's my opinion, of course. It is easier for me opening a full screen DOS box and working with MSDOS when I am coding in MSDOS. Typing a couple of commands won't kill you.

Quote:Relative paths don't work unless you're using a bat file or you have already compiled your program. . .

I think your definition of "work" is different than everybody else's.

Relative paths always work. They point to a path relative to the default directory.

(You can change the default directory while in the IDE you know...)

To back up Plasma's words...

Relative paths always work unless you are a total, absolute, and utter idiot OR are dumb enough to put the directory of the EXE for a game in your PATH environment variable, and then from a command prompt, type the program's name from another directory. Yes, then a relative path will fail. However, I'm pretty sure than 99% of the people on this forum are not quite so dumb, first of all, and second of all...whenever I start up a new project, I always ALWAYS have a base install of QB that gets copied to the project directory. It's less than 1MB, and eliminates a lot of the hassles of fumbling with directories. So yes, relative paths always work...provided you are relatively intelligent.

EDIT: And whining about it not working as sourcecode is lame. While a game is in development, you need to make sure it is able to work, period. This involves taking any steps necessary in your programming environment to ensure its proper execution. Virtually everyone here is smart enough to figure out how to do this.

Quote:I think your definition of "work" is different than everybody else's.

Relative paths always work. They point to a path relative to the default directory.

(You can change the default directory while in the IDE you know...)

Very funny. In the context of what TechFalcon was saying, one will not be able to immediately access the directory where the BAS file resides unless using a BAT file. Are you going to argue with that, too?

Quote:To back up Plasma's words...

Relative paths always work unless you are a total, absolute, and utter idiot OR are dumb enough to put the directory of the EXE for a game in your PATH environment variable, and then from a command prompt, type the program's name from another directory. Yes, then a relative path will fail. However, I'm pretty sure than 99% of the people on this forum are not quite so dumb, first of all, and second of all...whenever I start up a new project, I always ALWAYS have a base install of QB that gets copied to the project directory. It's less than 1MB, and eliminates a lot of the hassles of fumbling with directories. So yes, relative paths always work...provided you are relatively intelligent.

Um, you have no idea what I was talking about, do you?

Quote:EDIT: And whining about it not working as sourcecode is lame. While a game is in development, you need to make sure it is able to work, period. This involves taking any steps necessary in your programming environment to ensure its proper execution. Virtually everyone here is smart enough to figure out how to do this.

Right... now you realize what I'm talking about. What's your point, anyways?

Er, if QB is in your path you just change to the project dir and type QB...if it's not, then you change to your QB dir, launch the IDE, then change the default directory to that of the project via a shell or chdir in the immediate window.

It's not rocket science.