allegro | Go bindings for the allegro graphics

allegro is a Go library. allegro has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

Allegro requires everything to be called from one hardware thread. You will have to do this yourself. I recommend using a pattern similar to the one described here. This will allow you to run functions in a single, unchanging hardware thread. There are some allegro functions that do not require this thread locking, but they're not well documented, and shouldn't be relied upon. Documentation? Ha! Read the allegro docs. Almost everything mirrors the allegro C library (major exceptions are anything to do with iteration). Things have been "object orientified" somewhat: al_destroy_display -> display.Destroy and the like. If you want to do your own stuff using the C api, you can convert most of the types simply by casting the types (i.e. (*C.ALLEGRO_DISPLAY)(disp) and vice versa). There are a couple of exceptions (well, just LockedRegion), but you can use the .GetRaw() method to get the raw pointer/data. That said, casting things outside of the allegro package does seem rather to not work, which is a shame. One problem with the way that iteration is done in this package is that it has the potential to leave a lot of goroutines lying around. For example, if you iterate through the sections of a config, and then break instead of letting the iteration finish naturally, the go routine will never be collected. To avoid this in handling events, you can clean up any calls to GetEvents by calling EventSource.Stop on any of the sources that were passed to GetEvents.