FBIde doesn't work with linux... this is the linux forum.

The way of
MyObject.Text = "SomeText"
is called a property, and it's actually another way of calling a function (declared as property set). FreeBASIC doesn't support that, so you'd have to call an Update function every time you did that and I doubt anyone would like that.

I would think you'd make a .def file telling all the exports for when you build your DLL.

I'm don't know much about mutexes, but I believe that named mutexes are used to allow only 1 instance of the program (on Windows, returns ERROR_ALREADY_EXISTS or something like that). So shouldn't (or isn't) there an optional name parameter for MUTEXCREATE?

You should probably look into using Mutex objects for thread syncronization.

http://msdn.microsoft.com/library/defau ... emutex.asp
http://msdn.microsoft.com/library/defau ... ctions.asp

If you are doing this for just your game, I would make it an option in your game, that defaults to "OFF", just to be on the safe, legal side. And don't make another program, just catch the keystrokes in the game and record them... and ONLY if the user has detected them. I for one wouldn't ...

If the POLINK program works like microsoft linker, you should include the 'lib' prefix for each static library, since it is part of the filename. Also, you might want to try creating new import libraries. I'm sure it comes with some sort of tool that creates import libraries compatible with it. Also...

but FreeBasic uses the GNU linker, so it may be compatible...

What about external resources (images, models, sounds, music)? Is somebody else going to be doing these?

For 2, there is a cross-compile option on Windows. Try
fbc -target dos filename.bas

Very sorry, but it would be easier to understand the questions if you looked up the terms first. The "little words below the window title" is called a menu, because it contains a list of the functions available in the program. The "toolbox" is called a toolbar. There are function...

Try this:

It appears that MessageBox is actually called _MessageBoxA@16. You can figure this out by looking at the size of the parameters (int + pointer + pointer + int = 16). I'm used to NASM syntax though. You'll have to figure out the rest. Maybe FB's string handling is kind of odd. MessageBox expects a Nu...

Many of these things you can implement yourself with macros and other supported features. For example,

#define CURRENCY DOUBLE

Use the function SetWindowLong using the GWL_STYLE flag and don't include the WS_MAXIMIZEBOX style.