[waffle] [GSOC2014] Current design/implementation + the infamous corruption

[Emil Velikov]

On 06/06/14 09:09, Juha-Pekka Heikkilä wrote:
> On Fri, June 6, 2014 9:45 am, Chad Versace wrote:
>> On Thu, Jun 05, 2014 at 05:49:04PM +0100, Emil Velikov wrote:
>>> On 05/06/14 03:19, Emil Velikov wrote:
>>
>>>> waffle_window_create(config, w, h)
>>>> + waffle_window_resize() // Reuse the window... and boom. Any
>>> suggestions on
>>>>                          // how to resolve this, or should we mandate
>>> that
>>>>                          // this is not a valid usage of waffle ?
>>>>
>>> There is no use case in piglit + waffle{examples/utils} where one would
>>> create
>>> multiple windows for a single config. I might just add a lovely assert
>>> and
>>> don't worry about this too much.
>>
>> Don't worry too much about getting mutliple windows to work. Last
>> I checked, multiple window support was broken in the Android backend
>> too. It's perfectly ok to aim for imperfect good-enough during Waffle's
>> initial Windows support.
> 
> When making Android version of Waffle on top of Ice Cream Sandwich I saw
> process becoming unstable when asking for second surface control object
> (read: window) within same process. The problem was on Android
> SurfaceFlinger side thus I decided just to ignore the problem of multiple
> windows.
> 
> On Android Waffle does what is asked from it and if the process segfaults
> because of this I left it up to the programmer to figure how to behave on
> chosen OS. Though, asserting this might be good idea to highlight what
> went wrong.
> 
I'm afraid that my approach will not be beneficial to android, as I use
wgl_window::created that me keep track of things.

-Emil

> /Juha-Pekka
>