Global listeners need to be registered in the IListenerRegistrar in order to receive a notification via a callback when an event has occurred. Global listeners will receive notifications about all events of a specific type.Since many method calls are asynchronous, there is a mechanism for receiving responses within a callback that is based on implementing special interfaces called listeners that derive from the IGalaxyListener interface. It calls GetError() and throws appropriate exception if there was an error during the last API call. Global function ThrowIfGalaxyError() can translate errors to C++ exceptions. Every call to an API method resets last stored error, therefore you should check for errors after each call. They can be accessed with global functions called User(), Matchmaking(), Networking(), ListenerRegistrar(), etc.įor every frame you should call ProcessData() to process input and output streams.Įrror occured on call to Galaxy API can be obtain by calling GetError(), which returns NULL if there was no error. IUser, IMatchmaking, INetworking, IFriends, IListenerRegistrar, ILogger. You can control your Galaxy Peer through interfaces for specific feature sets, e.g. You can either include only the header files with the data structures and interfaces you need, or simply include the file called GalaxyApi.h that includes all the other files. The Galaxy API is divided into multiple header files. Only Galaxy Peers that use the same Client ID can interact with each other. You will be provided with a pair of Client ID and Client Secret that are to be used when calling Init().Ĭlient credentials identify your game within Galaxy. In order to use the Galaxy API, you should request special client credentials from GOG.com for each game you develop. Developing a game with Galaxy needs to start from linking your application to the following libraries:Īll libraries are loaded dynamically, so they have to be placed in the same folder as your executable.
0 kommentar(er)
