If you have questions regarding trivial-gamekit, feel free to shoot them here or in #lispgames IRC channel at freenode.net. I'll try my best to answer them as soon as possible.
Useful links:
* Getting Started guide
If you have questions regarding trivial-gamekit, feel free to shoot them here or in #lispgames IRC channel at freenode.net. I'll try my best to answer them as soon as possible.
Useful links:
* Getting Started guide
I'm working through your getting started guide and get an error on first example in the Input section (the bind-cursor form):
There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION BODGE-CONCURRENCY::INSTANCE-LOCK-OF (1)> when called with arguments (NIL). [Condition of type SB-PCL::NO-APPLICABLE-METHOD-ERROR]
CuriousCain, thank you!
smithzv, I do agree that's quite inconvenient - gonna fix it in the next gamekit release (https://github.com/borodust/trivial-gamekit/issues/39)
I'm having trouble restarting my game with trivial-gamekit. Evaluation aborted on #<SIMPLE-ERROR "Only one active system of type 'appkit-system is allowed">
Is there a way to kill the 'appkit-system thread? I tried with (stop) but it's not working. My workaround for this is to close slime and reload everything, but its really annoying. Any ideas?
*edit*
The game runs fine for now. I think my code was breaking something and SBCL became unresponsive, not destroying the game process, even with (stop) calls.
Awesome library by the way! Very simple, it helps me a lot since I'm new to the lisp world.
If you drop into debugger, don't hit 'abort restart, invoke either 'rerun-flow-block or 'skip-flow-block after fixing a problem. If that doesn't help and you keep getting an error - still don't 'abort, but run (gamekit:stop) in the REPL and then invoke 'skip-flow-block restart - that should shutdown the engine gracefully, and you should be able to #'gamekit:start your game again. If all goes left, then just restart the implementation (should be a very rare thing). That's not very convenient and gonna be fixed in https://github.com/borodust/trivial-gamekit/issues/40.