* Corresponding author: integrative analysis of a lacustrine carbonate succession from Butte Iouton hill (Vistrenque basin, SE France) brings new insights into depositional models and stacking patterns of oolitic saline lake margins and provides new details regarding the late Eocene paleogeography of southeast France. Université de Montpellier, Institut des sciences de l’évolution (ISEM), Campus Triolet, CC065, 34095 Montpellier cedex 5, Franceįédération de recherche sciences chimiques Marseille FR 1739, Pôle PRATIM, 13331 Marseille cedex 03, France I think that would work, though it would require a fair bit of rewriting of the existing input routines.Nazim Semmani 1, François Fournier 1 *, Philippe Léonide 1, Monique Feist 2, Sarah Boularand 3 and Jean Borgomano 1Īix-Marseille Univ, CNRS, IRD, Coll France, CEREGE, 3, place Victor Hugo, Case 67, 13331, Marseille cedex 03, France On SDL_KEYUP, if there's a pair with that keysym, send an internal Oolite key up event for its unicode value, and remove the pair, otherwise send the key up event for the keysym.Send an internal Oolite keydown event for the unicode value if available and the keysym if not not an arrow key, modifier key, etc.), pair the unicode value and the keysym. On SDL_KEYDOWN, if the key has a unicode value (i.e.So what we could do, to get around SDL_KEYUP not containing unicode info, is: ~ -> reported as ~ in unicode, but #+ shift as the keysym+modifier Experimenting with that C code, it looks like the SDLK_* constants are mapped to the lower-case keyboard layout, but you have to do Shift- and Ctrl- keys yourself, through some form of magic. It claims - that SDLK_* constants are mapped to the current keyboard layout. I'll post an example stdout.txt from a test run as soon as I get the opportunity to work again on the Italian layout laptop. Right now I can't think of a way to handle this properly, although it is also true that I did not verify the correctness of that comment myself. The bad news is that as per comment in the example code, SDL_KEYUP does not contain unicode information. This means that for example, the backslash of the Italian keyboard, found in the location of the backquote on the US layout is now read as backslash on the unicode keysym member. The good news is that the keysym.unicode member seems to be getting the correct information, provided that I use the Italian keyboard setting. I tried both English and Italian language keyboard configurations when doing the test. This is the same regardless of what the language setting is in Windows. So, even if we do break the KEYCODE_DOWN EITHER and KEYCODE_UP_BOTH macros, we will probably still be reading positional information from the keyboard. The keysym.sym codes, which is what we use in Oolite for reading the input are always returning the US keyboard layout codes, even with this very basic example. I can post actual results later, but what I noticed is this: I built and run the Example 3-11: Interpreting Key Event Information from this page:Īnd run it on a laptop with Italian layout. I made a small test to verify whether SDL is responsible for what we are seeing or not.