@Swoop

Just for the record, dvplayer uses ffmpeg library to decode all those files, and ffmpeg is far from being a one-man project. :)

@afxgroup

OpenRA is indeed "alpha" in general, but its issues have *nothing* to do with high stack. Setting 30MB is really useless. Maybe it could sometimes "hide" some overrun bugs, but that's it. And it wouldn't prevent from overwriting other local vars anyway. And by the way, most of OpenRA issues are about unitialized vars and heap management. Stack usage in-game is less than 16kB most of the time, and actually rather close to 2kB in game.

I still wonder why some people consider setting insane values of stack can help in any way. It looks like voodoo magic to me.

@orgin

Port Ambient, it's open source and has almost everything you need.

(/me is already outside)

Right, -1 is a valid return value, allowing any resolution to be used, but then the application can't really know what resolution is valid and what's not and i don't see any other way in the sdl api.

In our case, and especially in fullscreen mode, it's a good idea to return the list of available screenmodes to avoid any weird (too small or too large) display, because, as far as i know, OS4 can't create dynamically new screenmodes.

And in window mode, it's still an issue as well, because it should only list resolutions inferior to the wb screen resolution, which the application can't retrieve using only SDL api.

So, as you see, hardcoding resolutions and praying that they are really available is certainly not the best idea.

@salass00 & afxgroup,

don't you think it would be a much better idea to implement SDL_ListModes() properly (i.e returning an array of available screenmodes) instead of hacking every single application/game using this function? Besides, your patches won't probably be welcome, as it means you want to submit some very particular cases to a "clean" and supposedly portable game .

What's the point of having SDL on OS4 if it's not compatible with the SDL specifications?