Bug 209737 - Actions not available until I create a "dummy" action
Summary: Actions not available until I create a "dummy" action
Status: RESOLVED FIXED
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Esben Mose Hansen
URL:
Keywords:
: 194844 206932 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-07 12:45 UTC by gerlos
Modified: 2009-11-24 16:14 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gerlos 2009-10-07 12:45:18 UTC
Version:           0.9.7 (using KDE 4.3.1)
OS:                Linux
Installed from:    Mandriva RPMs

After I updated to KDE 3.1, I found that the actions list in Klipper is empty. 

If I copy to clipboard an URL and I have enabled actions, I see that nothing happens, but if I create a "dummy", empty action in the actions list in the configuration window, I got back a lot of "standard" actions. 

They seem based on mime-type of "things" that went to clipboard, eg. if I copy an URL I see a list of browsers and editors, if I copy a JPEG file I got a list of image viewers, and so on.

It seems that the only way to get these standard actions is to add an action to the list. I feel this behaviour is somehow wrong, since a lot of people would find it only by accident.
Comment 1 Esben Mose Hansen 2009-10-07 14:20:10 UTC
Surely, the KDE version is a typo. I think there is a bug where the standard actions are only available if there is a regular action. Surely a easy job to fix, if someone is up for it. The fix should also include a way to disable standard actions.
Comment 2 gerlos 2009-10-07 16:26:41 UTC
(In reply to comment #1)
> Surely, the KDE version is a typo. 

Yes, I missed a "4". I meant KDE 4.3.1 :-)
Comment 3 m.wege 2009-10-09 19:05:51 UTC
*** Bug 194844 has been marked as a duplicate of this bug. ***
Comment 4 Esben Mose Hansen 2009-10-09 20:19:45 UTC
Just in case someone is planning to take me up on this: I had to fix this bug while working on actions that interact with the clipboard history. So a fix will hit SVN in the next few days, maybe even tonight.
Comment 5 Sérgio Basto 2009-10-09 22:36:54 UTC
*** Bug 206932 has been marked as a duplicate of this bug. ***
Comment 6 Sérgio Basto 2009-10-09 22:41:27 UTC
hi
my bug #206932 is objectively equal to this.
but bug #194844 is about other problems with klipper , when actions works in some cases but don't works in others cases. 
my 2 cents.
Comment 7 Esben Mose Hansen 2009-10-10 08:12:29 UTC
bug #194844 turned out to be 3 separate things: The Qt upstream bug, the fact that some applications are by design ignored by Klipper, and finally this. But I cannot close a bug as UPSTREAM, DUPLICATION and INVALID at once :)
Comment 8 Esben Mose Hansen 2009-10-10 09:52:39 UTC
SVN commit 1033402 by esben:

Make it possible to have actions that are not invoked automagically
and have the output of actions interact with the clipboard history.
This should make it possible to manipulate the clipboard history
in vairious ways.

Some neccessary work along the way:
Rework editActionDialog
Actions were not checked when no user actions were available.
BUG: 209737

 M  +1 -0      CMakeLists.txt  
 A             clipcommandprocess.cpp   [POSSIBLY UNSAFE: setShellCommand] [License: GPL (v2+)]
 A             clipcommandprocess.h   [License: GPL (v2+)]
 M  +250 -70   editactiondialog.cpp  
 M  +3 -2      editactiondialog.h  
 M  +65 -17    editactiondialog.ui  
 M  +5 -2      history.cpp  
 M  +28 -38    klipper.cpp  
 M  +1 -1      klipper.h  
 M  +65 -75    urlgrabber.cpp  
 M  +36 -13    urlgrabber.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1033402
Comment 9 Maciej Mrozowski 2009-11-22 16:26:25 UTC
Dammit, forgot to CCBUG.. anyway backported to 4.3 branch. Thanks for the patch!
Comment 10 Maciej Mrozowski 2009-11-24 14:53:20 UTC
Hmm, this commit introduces new strings, so job for translators. Should I revert my backport
Comment 11 Frederik Schwarzer 2009-11-24 16:14:11 UTC
No, leave it now. As far as I could see, it is a bugfix and only new strings were introduces (no existing strings altered).
This means, if the translators do nothing, it is not a regression l10n-wise.

But ask in #kde-i18n on freenode to get a more official statement from tsdgeon, Chusslove or blueck.