Luca, I ran into the same issue - the new windows always start on landscape - and used the same workaround - checked the screen resolution and when taller set the portrait attribute. And yes, I believe you are right, setting the attribute will disable the autorotation for the new window (does not affect the original one though). I tried to set the portrait attribute and then the autorotation on the new window but then the window will start again on landscape mode. One workaround I did not try was to set the portrait attribute and a timer for a little after the window is showing to set the autorotation attribute. It seems that the "autorotation dispatcher" only check the window attributes after the window is showing and/or on a predefined schedule (maybe it is a bug). My application (macuco2 on the dev repository if you want to try) seems to take some time after starting to start receiveing the "signals"... Sometimes only starts after you show the menu for the first time. Felipe
> Felipe, you're absolutely right: once set the autorotation flag in the > topmost window of the stack, the others seem to retain it. > Only issue remaining is that once you open a new stacked window, it > starts in landscape mode, disregarding current device orientation, *but* > its child widgets are layed out respecting the correct screen > proportions. I can check for screen geometry and set the landscape or > portrait flag accordingly, but I'm wondering if this will disable the > accelerometers from then on (ie: overriding the autorotation flag set > before). Any clue on this? > > -- > Luca Donaggio
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
