Daniel d'Andrada
2011-04-28 11:37:12 UTC
Hi,
Until now whenever the orientation changes all QGraphicsItems in the
scene were getting a MOrientationChangeEvent. This meant not only the
items in the scene windows currently being rendered (scene window state
== Appared, e.g. current page) were getting this signal but also all
other items that reside in scene windows that are currently hidden (e.g.
all pages in the back stack or pages from other tabs).
From libmeegotouch 0.21.9-1 onwards (version not tagged yet) only items
residing in scene windows whose state is different than Disappeared
(e.g. items in the current page) will get MOrientationChangeEvent. When
a disappeared scene window enters again the screen (leaves Disappeared
state) its items will get MOrientationChangeEvent with the current
orientation if they happen to have an outdated orientation. That
optimization will happen only if your scene is being handled by a
MSceneManager (such as in MApplicationWindow case). Barebone MWindows
without a scene manager will still have all their items notified as usual.
No change is need in your application unless your code relies on having
an MSceneManager *and* getting MOrientationChangeEvents for every single
item in the scene whenever the orientation changes. We didn't spot any
such use case so far.
Regards,
Daniel d'Andrada
Until now whenever the orientation changes all QGraphicsItems in the
scene were getting a MOrientationChangeEvent. This meant not only the
items in the scene windows currently being rendered (scene window state
== Appared, e.g. current page) were getting this signal but also all
other items that reside in scene windows that are currently hidden (e.g.
all pages in the back stack or pages from other tabs).
From libmeegotouch 0.21.9-1 onwards (version not tagged yet) only items
residing in scene windows whose state is different than Disappeared
(e.g. items in the current page) will get MOrientationChangeEvent. When
a disappeared scene window enters again the screen (leaves Disappeared
state) its items will get MOrientationChangeEvent with the current
orientation if they happen to have an outdated orientation. That
optimization will happen only if your scene is being handled by a
MSceneManager (such as in MApplicationWindow case). Barebone MWindows
without a scene manager will still have all their items notified as usual.
No change is need in your application unless your code relies on having
an MSceneManager *and* getting MOrientationChangeEvents for every single
item in the scene whenever the orientation changes. We didn't spot any
such use case so far.
Regards,
Daniel d'Andrada