In case anyone ever manages to lose their FBIde settings, this info should help them get it back.
If you go into View->Settings and click on the FreeBASIC tab, then the settings should look something like this:
The Compiler path may vary depending on where you installed the FreeBASIC compiler, and you may have changed the Help file line if you downloaded an update to the documentation, but the Compiler command and Run command should look pretty much as above.
The Compiler command may have additional compilation parameters after it (e.g. -lang fblite)
There are a few modifications you may also find useful:
- Compiling with -exx
This enables the largest possible amount of error checking, aborting the program on things like problems opening files, or going out of bounds on an array.
"<$fbc>" "<$file>" -exx
- Compiling with -s gui
This prevents the program from opening a console window ("DOS Prompt") when it starts. Useful for programs that only use a graphics screen or a GUI. It can be used in conjunction with -exx, but you won't get to see any errors that are printed.
"<$fbc>" "<$file>" -s gui
- Leaving the command line window open when the program finishes
This basically consists of wrapping the Run command in cmd /c [Run-command & pause], which opens up a command window that does the Run Command, and then runs Pause to wait for a keypress before closing. This is a good alternative to putting Sleep at the end of a console program, and also stops the window closing if the program aborts with an error, allowing you to see the message returned. So it's good to use with '-exx' (not so useful with '-s gui').
cmd /c "<$file>" <$param> & pause
This should work on any version of Windows that uses cmd, e.g. Windows 2000/XP/7. (It would be good to hear feedback on how it works on Windows 8.)
UPDATE: fxm suggests wrapping the command(s) in an additional set of quotes:
cmd /c ""<$file>" <$param> & pause"
This should prevent things breaking in case <$file> contains spaces or <$param> contains quotes.