Re: [Announce] Pierogi - a universal infrared remote control app
 

There's a couple of Alpine config files in LIRC, I'll add them into the next update!

Re: [Announce] Pierogi - a universal infrared remote control app
 

@Copernicus
I used one of the first versions of pierogi, it worked quite well in portrait mode. Recently I installed the latest one, and whole UI in this orientation is a mess (button icons/tabs, panel selection etc). pierogi greatly expanded its functionality but portrait UI was left behind.
But, given specific nature of pierogi (which is effect of N900 IR diode placement), I don`t think that more time investment on coding the portrait mode is rational any more - quite opposite.
If to actually use pierogi one must hold phone in landscape orientation, lock (hard code) pierogi in landscape orientation and drop portrait support completely - because You can`t use it effectively in that mode anyway. Simple as that.
From my experience, it`s a case with many (all?) "remote control" apps out there - orientation is imposed by construction (diode placement) of the phone.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Ah, I am guessing you are a CSSU user? :) In fact, I chose to design Pierogi as a landscape-only app, precisely for the reason you specified. Pierogi has been "hard-coded" to work only in landscape mode from the very beginning. However, there is a "forcerotation" option in CSSU that enables portrait mode for all apps, whether they want it or not. To stop this from happening, you'll either have to turn "forcerotation" off, or manually add Pierogi's name to the blacklist.

Re: [Announce] Pierogi - a universal infrared remote control app
 

I don't think you should write off getting a MicroUSB IR transceiver working. Then portrait will be really useful.

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.

tanrax and taixzo were/are having trouble with rotation in python (SimonKM and Saera respectively). There's a file made by thp that can when tweaked and added to the package can make the main.py file support rotation, for landscape only or portrait only applications.

http://talk.maemo.org/showpost.php?p...9&postcount=39

I know your not using python but you get my point.

Re: [Announce] Pierogi - a universal infrared remote control app
 

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...

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:

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. :(

Re: [Announce] Pierogi - a universal infrared remote control app
 

Absolutely true - it was the reason behind implementing forced-rotation (debuging/power-user tweaking). It was never meant as end-user way of doing things. Of course, as many things with CSSU, this provisional solution remained indefinitely (I'm also having forced rotation "on" all the time, with carefully micromanaged maintained blacklist).

/Estel

Re: [Announce] Pierogi - a universal infrared remote control app
 

So, hey, is there any way to ask the CSSU powers that be to change forced-rotation from a "blacklist" scheme to a "whitelist" scheme? The current mechanism penalizes those of us who have an actual valid reason to avoid rotation. If there are apps that are incorrectly avoiding rotation when they shouldn't be, I'd prefer they be singled out by the forced-rotation "feature" rather than folks like me. :)

Re: [Announce] Pierogi - a universal infrared remote control app
 

Hi Copernicus.

I just edited the compatibility list and added the Technics xx-HD350 series of Hi-Fi components. Lost my remote during a house move and when it tirned up again the batteries had leaked and destroyed it.

Any chance you could add that one. If you need any help let me know.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Edit: whoops, I thought you were asking to add a Technics keyset! :) I haven't been updating the devices list in a while, maybe I should do that... :)

Edit 2: Ok, me confused. :) :) Are the current Technics keysets working with the HD350?

Re: [Announce] Pierogi - a universal infrared remote control app
 

Hm, I was sure, that cssu support both blacklist and whitelist modes for forced rotation, and deciding which one to use, it's up to user? It's possible, that blacklist is more popular, as it was implemented earlier than whitelist (by few months).

As for convincing "powers behind cssu" to do anything, I'm absolutely out of this business, and I see it as hopeless task, (to say at least) - see whole embarrassing thing behind (not)including busybox-power into CSSU, for reasons "why". Only one person there, that actually *listens* to any arguments, if freemangordon, but he is focused (rightly so) on his own projects (including thumb variant of cssu), where he doesn't get into artificial obstacles in decision-making process.

/Estel