Bug 371993 - Spectacle - missing kioslave interface, no sftp, and no multi-instance capability
Summary: Spectacle - missing kioslave interface, no sftp, and no multi-instance capabi...
Status: RESOLVED DUPLICATE of bug 369174
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-02 19:27 UTC by David Rankin
Modified: 2016-11-02 22:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
snapshot of dialog at issue (24.36 KB, image/png)
2016-11-02 19:27 UTC, David Rankin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Rankin 2016-11-02 19:27:45 UTC
Created attachment 101980 [details]
snapshot of dialog at issue

KDE Frameworks 5.27, Spectacle Version 16.08.2 - Sorry for Any Inconvenience (that puts it mildly)

There is no kioslave interface in the save/save as dialog making it impossible to save the image to a remote directory. Why doesn't this rendition of ksnapshot have a normal save dialog. No matter where I am in KDE, I should have full dialog capability, just like has always been there since KDE3. An editable path component where the requested kioslave can be entered as a prefix to the path (e.g. sftp://server/path).


Next, there is no ability to run multiple instances of spectacle making it impossible to take a screenshot of this issue. Instead, you have to overlay a new snapshot of the save-as dialog on top of the already full image and use gimp or some other app to crop all the unwanted junk out of the image. Just make a new instance of spectacle launch on each press of 'print screen' like it always has. (it is much more useful that way)

I've attached a screenshot showing the current limited dialog that appears (I hope it is the right image, tooltip previews no longer work in this version of KDE)
Comment 1 Christoph Feck 2016-11-02 22:14:49 UTC

*** This bug has been marked as a duplicate of bug 369174 ***
Comment 2 Christoph Feck 2016-11-02 22:16:00 UTC
The second issue is bug 362616.

In the future, please report one issue per ticket.