InitGameAPIex

[Donone]

This will seem stupid, but with a terrible memory, and the need to look up InitGameAPIEx at infrequent intervals, I can never remember how I found it in the help file.
After a break, I have forgotten and have tried desperately to find it.

[zehlein]

Donone, I don't think you found it in the help file, it's simply not there (yet).

InitGameAPIEx(h$, &GameProc, 240, 320, false, 5, 60);

* h$: the GameAPI windows handle
* &GameProc: the adress to the GameProc procedure GameAPI should use
* 240: points in x direction for the GameAPI window
* 320: points in y direction for the GameAPI window
* false: no fullscreen (true: fullscreen)
* 5: GameProc/internal processing is called every 5 ms
* 60: draw at the screen at 60 fps

This should explain the parameters correctly, at least as far as I know.

[Donone]

Thank you zehlein, very useful, sorry for the late response.
I agree it is not in the help in the normal way, but I feel sure I found an indirect reference some time ago, hidden among other things.

[Mike Halliday]

D.

You can also load up GAMEAPI.ppl from the RUNTIME\LIBS folder and that will show you how the commands are made up (It will also show you how Alain has created the easier commands for all of us to use)

[Donone]

Thank you Mike, that will be useful.

[PointOfLight]

If you do end up finding initGameApiEx in your help file, I'd like a copy of that file :)* Seriously, though, the function does not exist in the help file yet.* Currently, most of the documentation in the help file refers to built in PPL functions, not the functions in the supplimental files Alain has created.

Just to give you a rough idea, there are 650+ functions native to PPL.* Doing a search on the files in the RUNTIME\LIB directory of the install, you'll find 586 instances between the words "func" and "proc".* I don't know if that translates 100% to an actual number of funcs and procs, but it's probably close.* That's over 1200 functions available to PPL users.

Of course, none of this is meant to be an excuse for not having more of this documented.* I work on the help file every chance I get.* I just need to quit my day job <img src=&quot;{e_IMAGE}emotes/default/sad.png&quot; style=&quot;border: 0px none &quot; alt=&quot;sad.png&quot; />

[Donone]

Well it took you a while to respond to this one PointOfLight, I expected you sooner.
If you read the first post I think you will find that it was not a criticism, nay, I know it wasn't.

Instead of giving up your day job; with your grasp of sympathy winning statistics you could become a politician. :-)
Just fun!
Thanks for the good job that you do under such strenuous conditions. We would really be in trouble without it.
BTW I'll swear I saw a reference somewhere within another item, but I am getting older.

[PointOfLight]

I might have missed something, but I searched the help file a couple of times and could find no reference to that function.* I will admit that I actually thought it was there at one time as well.* As for not getting here sooner, oddly enough the Help File Updates forum did not show up as having a new thread for me until just today.* Sorry about that <img src=&quot;{e_IMAGE}emotes/default/sad.png&quot; style=&quot;border: 0px none &quot; alt=&quot;sad.png&quot; />

I know you weren't criticizing either, but I still wish I had a more robust help file for you guys by now.* I've worked with a lot of different development environments over the years, and I know how much of a difference a good help file can make.* But it will be there one of these days :)

[Donone]

If it helps at all PointOfLight, when I believe I saw the entry referred to, it was NOT searchable. It was within the text of some other item. I don't know if the search actually searches every word in the help, only you would know that.
I have every confidence that one day someone will say 'here it is, buried in...'

We'll see.
Thanks again PointOfLight.