By the time the refresh signal gets processed and the buffer gets painted, the contents and the size of the original framebuffer pointer may have changed, causing bad repaints or even segmentation faults. Using the original pointer is a bit dangerous. You pass along the original pointer directly to the Qt4 front-end. My code relied on this buffer when I emited a Qt4 signal to draw the buffer. I noticed that you removed the static buffer in which I copied all the pixels from the original framebuffer pointer when phoneME tells me to draw the buffer. Yes, but I have not come around to integrate your changes into my build. You can also check the default rotate/portrait behavior in the MIDlet Settings - did you look at cvm code I pushed on gitorious and my build scripts? I created a new build in which I add the old command line parameters again, and mapped them on the new ones (portrait -> rotate, and noportrait -> norotate). I changed the naming, because if you enabled the old portrait option and if your display was already in portrait mode, then the midlet would be shown in landscape mode rather than portrait mode. If you used "-portrait" in some startup scripts, then this may explain this change in behavior. "portrait" and "noportrait" became "rotate" and "norotate" respectively. The code changes between the 6th and the 7th were not that significant, except for the fact that I changed some command line parameters, i.e. I tested the 7th, the 8th, the 11th neither of them was good (both started in landscape mode) and the 6th version was good. Thanks for your work, I hope you'll find the problem. So I may have to produce a few test builds to really identify which change caused the portrait mode issue. However, due to the ifdef macro, this code is excluded for the MeeGo builds (presuming you did not install the Maemo build on your MeeGo device).Īnother change is the fact I added multimedia and location features that rely on the Qt Mobility libraries. SetAttribute(Qt::WA_Maemo5NonComposited) SetAttribute(Qt::WA_Maemo5AutoOrientation, true) The reason why I ask is because I checked the source of 2 backups of March 5 and March 11, and I added a.o. Just to be sure: you did install the MeeGo builds and not the Maemo builds right? Sound was good, but didn't find the location.jad to check the GPS.Thanks for testing! The location feature was added afterwards, so that is normal. The march 7 release had good Opera Mini orientation, but the march 8 had not.
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |