Hey, a question for the CSSU folks: I've recently been getting more and more comments about how poorly my app (Pierogi) handles portrait mode. Now, this makes sense, because my app doesn't handle portrait mode at all; Pierogi (an infrared remote app) needs to use the IR LED, and as such, doesn't work very well unless you've got that LED pointed away from you. So I feel justified in locking the app to landscape mode.

However, the "forced-rotation" option of CSSU has apparently become extremely popular amongst users. Just today, I received one note that I could improve my app by locking it into landscape mode (which, of course, I've been doing since I started writing it), and another note that I could try to manually catch the DBUS rotation signal and thereby create my own "landscape lock" functionality that avoids the standard code that the forced-rotation option breaks. (I feel like my app is being penalized for using the official Qt rotation handler!)

I understand that "forced-rotation" was originally supposed to be just a debugging feature, but it certainly appears to be more than that today. So let me ask: is forced-rotation really still necessary? How much of a hardship would it be to remove it from CSSU? Or is it now a necessary feature?

And, if it is now more of a feature than a debugging tool, can it be modified to use a "whitelist" mechanism rather than a "blacklist" mechanism? That seems more logical to me. Ultimately, if we're going to force CSSU end-users to do extra work (by adding names to a list), I'd prefer that they do it when they want to change the default behavior of an app, rather than do it to get an app back to working the way it was designed...