Started by neroden, July 02, 2013, 07:34:11 PM
0 Members and 1 Guest are viewing this topic.
Quote from: kierongreen on July 06, 2013, 07:17:55 PMAs you say, until SDL 2.0 is officially released simutrans should stay with the existing SDL routines. However there could be both SDL 1 and 2 platforms supported until then. As the routines are separate from the rest of the code largely then maintaining both shouldn't be too much of a burden. What was the issue with multithreading?
Quote from: Yona-TYT on August 24, 2013, 04:33:19 AMThis will help hardware acceleration?
Quote from: meme on August 25, 2013, 10:08:06 AMWill be SDL2(.1) version for OS X? Performance of native simutrans with 1.2 SDL is horrible and I'm not happy that I have to use wine for playing simutrans.. But it's still better than nothing.
Quote@ArthurDenture - can you try RGB565 on your Mac and see if performance is still ok? Otherwise we'll have to figure out what's busted with RGB555 (psychedelic transition ground textures).
QuoteAlso, does your sdl2 branch compile? If so, you must be using a beta SDL2. The unicode member of keysym has been removed...
Quote from: TurfIt on August 26, 2013, 02:16:57 AMSDL_TextInput events would be fine if one is doing text input. But what about hotkeys / commands? Sometimes you actually want just a key. I'd love to know what to call in this new system so I'd get SDLK_AT when I type '@' instead of SDLK_2 and KMOD_SHIFT as separate... As mentioned, I can hack something for en_US, but en_GB might expect '"' from shift-2 instead of '@'; And of course the 4725 other keyboard layouts out there. The OS should handle this crap...
Quote from: Ters on August 26, 2013, 05:11:29 AMWhat if a hotkey is tied to 'ä'? That's a key on a Swedish keyboard, but requires two keypresses on mine.
Quote from: ArthurDenture on August 26, 2013, 03:48:13 AMI figured it out: just always do text input :-).
Quote from: TurfIt on August 27, 2013, 01:47:23 AMI'd expect the application to simply receive 'ä' from the OS.
Quote from: TurfIt on August 27, 2013, 01:47:23 AMWell, who'd a thunk? SDL documentation sure had me thinking the text input needed to be started/stopped for each entry field.