jsampson45 wrote: I assume that you installed COMatePLUS first before opening "Demo_Sendkeys.pb". How did you do this? Where did you put "Demo_Sendkeys.pb" so that PureBasic found it?
?
There is nothing to install, just unzip the zip in a path of your choice keeping the directory structure and it's ready to go.
Then you launch PB, navigate to the dir containing the demos and open open "Demo_Sendkeys.pb".
To use COMate in your programs instead, just mimic what that demo does.
Use includepath to specify the dir where you unzipped the archive, containing the main COMatePLUS.pbi file, and then include COMatePLUS.pbi. In turn, it will include other files as well, and that's why the includepath is needed.
As I said, PB try to resolve any include relative to position in the file system of the main file of your program. Includepath temporarily changes this.
The use of includepath could be avoided using the form XIncludeFile #PB_Compiler_FilePath + "MyFile.pb" inside the COMate source. But since that has not been used there you have to specify includepath instead.
Really, if you look at the help of all the include* commands + read the thread I linked, you *must* be able to sort it out.
Try some experiment writing a dummy program and putting some includes and maybe nested includes in it, like in my example. You have to grasp it how it works. When you do, you will be able to get any program posted in the forum and make it work on your system fixing any path problem (for example you could just add #PB_Compiler_FilePath in COMAte where needed to remove the includepath requirement).
Again, programs (especially include libraries like this one) written using the XIncludeFile #PB_Compiler_FilePath + "MyFile.pb" does not need any fix and they just work. So I suggest you to adopt that style in your future programs.
But first you need to understand how all this work, so try it. It's easy when you get used to it.
