Re: [Caml-list] SDL2 bindings, testers and feedback welcome

["Daniel Bünzli" <daniel.buenzli@erratique.ch>]

Le mercredi, 18 décembre 2013 à 09:05, Anthony Tavener a écrit :
> Something I'm not so keen on is that event types and event values aren't
> constants I can pattern match on, so I have a lot of "| t when t = "...
>  
> method process_event ev =
> match Sdl.Event.(get ev typ) with  
> | t when t = Sdl.Event.key_down ->
> begin match Sdl.Event.(get ev keyboard_scancode) with
> | t when t = Sdl.Scancode.s -> thrustp <- {thrustp with z = 1.}; true
> | t when t = Sdl.Scancode.w -> thrustn <- {thrustn with z = 1.}; true
>  
> These are matchable constants in sdlcaml.  
Actually that's something in the TODO:

https://github.com/dbuenzli/tsdl/blob/master/TODO.md

I don't think it's useful to convert let's say Sdl.Init enumerants to variants as those are mainly used for setting up state and less likely to be pattern matched upon. But at least functions from Sdl.{scancode,keycode} to an polymorphic variant will be added. Feel free to make your desire more precise in the issue tracker.  

> With Tsdl, the constants are brought in  
> as let-bindings... looks like Daniel has something nifty to make this a lot easier
> but I haven't looked into it yet.

Not so nifty, you still have to enumerate them. A C program outputs them, that's here:

https://github.com/dbuenzli/tsdl/blob/master/support/consts_stub.c
  
> Next is figuring out why my game controller isn't detected, and maybe plugging in
> a joystick and another kind of controller too. First, time for some sleep. :)

Just want to mention that if you are not sure whether the problem lies in the binding or in SDL itself there's a minimal C example with compilation instructions that you can use to try to reproduce the problem in: cd `opam config var tsdl:doc`

Best,

Daniel