Summary: | Remote control support (lirc) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Antonio E. <aironmail> |
Component: | Portability-Interroperability | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | CC: | caulier.gilles, gschintgen |
Priority: | NOR | ||
Version: | 0.8.2 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Sentry Crash Report: |
Description
Antonio E.
2005-09-26 01:19:54 UTC
yes thats a nice idea. You could use dcop for this. So digikam devs need to have these dcop functions that we can link it to lirc/kde lirc server ;) Greets Yes, dcop would be pretty good for this purpose. dcop interface have been added to digikam to current svn implementation. It will be available to 0.8.1 release. Gilles Caulier Cool! It's really nice to read that :). Thanks!!! uhum? dcop interface is added but not any functionality in regard to this report. I see. Well, at least it's a first step to make it possible. I hope that the functionability could be added in the future. Just a question, having the dcop implemented, what else needs to be implemented to communicate digikam with the kdelirc? I've been trying to find in the amarok sources were is the lirc support done but for now I haven't found it, just the dcop interface. Thanks. AFAIK This should be enough. You can connect dcop to lirc by using the kde lirc server. I'm doing this with amaraok. That is what I thought, but I can't. I'm using the kde-lirc with amarok too, for a year. When I open the kde-lirc dialog (IRKick), when I try to add a new action, I can select amarok, KsCD,... but digikam is not there. That's why I think that dcop is not everything that we need to use the kde-lirc. But, browsing the amarok sources I didn't find any line referring lirc only dcop. That's why I think that the support is mostly done, but some little thing is avoiding digikam to be controlled from kde-lirc. At least I can't see digikam from the irkick, I don't know if other people can and it's a local problem. Thanks for the comment. Cyrill, you are totally right. I can use now digikam using irkick. I've opened the irkick configuration dialog, pressed add and then selected to add manually an action to a running application. From there I can access to digikam. It's a pitty that digikam is not displayed in the default apps in the previous menu like amarok, kaffeine,kdetv,... but I can live with that. After selecting the desired button from the remote controller, I open the digikam tree entry in the application list, and from there I can access to the entire dcop interface. Then I have to play from the command line, because configuring lirc throw dcop is not so intuitive for normal users. I make an example of how I have set the forward button of the remote controller to show the next image in the Image Editor. In the command line I type: dcop (to get the name of the apps, in my case digikam-25053) Now I get the available actions for the editor: dcop digikam-25053 "Image Editor" actions I find the one that I want: editorwindow_forward To test it I type: dcop digikam-25053 "Image Editor" activateAction editorwindow_forward It works. So I go to the irkick and I add an action, setting the forward button, I open the digikam tree. Then I select the Image Editor. In the function list I select: activateAction. I press next, and I get a new text field asking for the action to execute, so I type: editorwindow_forward. After that I press finish, and it's done. I press apply. I test it with the remote controller and it works nicelly. As we see, the control of digikam with a remote controller is working perfectly using dcop. To me it's good enough (you can't believe how happy I feel setting this), but I think that it's very complex to set it for normal or new linux users, specially if they don't know a bit of dcop. It would be nice to have an easier way to set these action, like for the applications than I commented above. I repeat, I don't need it, but maybe other people... As the kde-lirc support is done, I don't know if we should close this issue or let it opened. I want to say thanks again for adding the dcop support. Playing with dcop I found a bug, that makes digikam to crash (I'm using 0.9svn). If I have the Image Editor, and I make: dcop digikam-2830 Digikam activateAction album_forward Then, digikam crashes. It happens always. No, it's worse, it happens always; even with the Image Editor hidden. Hi again... Probably there is just a list with apps and predefined actions in irkick... Not sure though, because that would be no good strategy :) I've created a new bug for the crash #132957 #14 ==> ok Antonio, we will take a look... Gilles Caulier Antonio, This entry still valid. LIRC can be used as well with digiKam now. I can close this file ? Gilles Caulier Well, this week I'm not at home, which is where I use Digikam. I haven't played with lirc for around 3-4 months so I haven't tested the current status. But, if you think that the support is working, then yes, probably we can close this file and then open new ones in case of if any problem is found; well that, unless if you'd like me to test the lirc support when I'll be back at home next Monday. In that case, is fine with just testing 0.9.4 or 0.10 has different code to manage it? Antonio. Antonio, Yes for 0.9.4-beta1. 0.10.0 do not use DCOP with KDE4, but DBUS. You can test it too, but this version still i alpha stage. take a care. Do not use it in production Gilles Caulier OK Gilles, I'll give it a try on next week at least the version 0.9.4, and I'll report how it behaves. Thanks, Antonio. Andi, This entry is fully relevant of digiKam DBUS interface... We just need to export digiKam actions, that all... Gilles Antonio, What's new about this entry ? Gilles Caulier Gilles, sadly I can't test this functionability as my lirc device passed away. Someone can provide any feedback with an IR remote control... Gilles Caulier New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? This will never implemented in digiKam... Gilles Caulier |