Thread: [Announce] Pierogi - a universal infrared remote control app
View Single Post
Copernicus's Avatar
Copernicus is offline Copernicus
2012-10-26 , 17:32
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#795
Originally Posted by sixwheeledbeast View Post
I don't think you should write off getting a MicroUSB IR transceiver working. Then portrait will be really useful.
I'd support that idea as well, if I wasn't so nervous about the fragility of the N900's usb port. I'd prefer to use that port as little as possible...

The problem with forced-rotation is that you have to support it to switch it off.

Because of CSSU and force-rotation many applications have Auto/Landscape/Portrait built into the settings, if you don't you have no option but forced rotation.
But, isn't this kind of redundant? I've only been programming in Qt, but Qt already has full support for Auto/Landscape/Portrait gui modes, as well as full control over when and how you switch between these modes. Pierogi itself is using the following command:

Code:
mainWindow.setOrientation(
  MainWindow::ScreenOrientationLockLandscape);
What the CSSU's "forced-rotation" does is to disable this mechanism. If I'm reading it right, that Python script (apparently taken from the gPodder app, from the comments at the top of the file) is using a different mechanism, directly grabbing the DBUS notification signal and working off of that -- if so, it is doing the same work that the Qt system is doing, but apparently in a manner that is missed by the "forced-rotation" thing.

It's my understanding that "forced-rotation" was always meant to be used as a debugging tool, not as a feature. I think it would be unfortunate if all apps must in future avoid the built-in rotation support of Qt and manage rotation signals manually, just because a CSSU debugging tool has become so popular.
 

The Following 2 Users Say Thank You to Copernicus For This Useful Post: