| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Change-Id: I453438fee92f18c983c1bef04c68b24a7ff72cf9
Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
Reviewed-by: Mika Salmela <mika.salmela@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If the context exists at renderer deletion, it is possible that
it no longer has valid surface, which means it won't be possible
to set it back to current if we change context for deletion cleanup.
Since the current context will be one of our shared contexts anyway,
there is no need to do a dummy context for cleanup unless the current
context is null.
Change-Id: Ibabe081742beb975ee848ccb3690703ef5b027a9
Reviewed-by: Mika Salmela <mika.salmela@digia.com>
Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
|
| |
|
|
|
|
|
|
|
|
| |
Context was not getting properly cleaned up in cases where
render thread stopped before the cleanup took place.
Now we ensure that required cleanup is done before context
thread terminates.
Change-Id: I1489914dafec928eebb69bac737f6f858ff49432
Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
|
| |
|
|
|
| |
Change-Id: Ib93917992c9cd8e744d4f8156271614893f8679e
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
|
|
|
Change-Id: Iff97d020ef6104d266dbc53931e44d494b415800
Reviewed-by: Tomi Korpipää <tomi.korpipaa@digia.com>
|
