SourceForge has been redesigned. Learn more.
Close

#107 Drag-and-drop foo.jpg behaves different from `gimp foo.jpg`

Incorrect_behaviour
closed-invalid
ROX-Filer (85)
5
2012-12-02
2012-11-26
No

Arch Linux 64bit (rolling release distro)
GNU Image Manipulation Program version 2.8.2
ROX-Filer 2.11 | Compiled with GTK version 2.24.6 | Running with GTK version 2.24.13

I use the context menu in ROX-filer to open foo.jpg in GIMP, which invokes `gimp foo.jpg`. If I then use "File/Export to", the suggested file name is "foo.jpg" . (Correct behavior).

If I instead drag and drop "foo.jpg" from Rox-Filer into the empty GIMP main window to open it and try to use "File/Export to", the suggested file name is "Unknown.png". (Incorrect behavior).

In Thunar (another file browser) the behavior is correct.

This indicates that Rox-Filer and Thunar use a different method when dragging and dropping. It is not clear whether it is the fault of GIMP or of Rox-Filer's method, that Rox-Filer's method is inconsistent with command-line opening of the file, which is why I report this issue on both GIMP and ROX trackers.

Report on GIMP's tracker: https://bugzilla.gnome.org/show_bug.cgi?id=689087

Discussion

  • Thomas Leonard

    Thomas Leonard - 2012-12-02
    • assigned_to: nobody --> tal197
    • status: open --> closed-invalid
     
  • Thomas Leonard

    Thomas Leonard - 2012-12-02

    I see this too with Gimp. However, dragging from ROX to other programs works correctly.

    ROX-Filer offers several targets, including "text/uri-list" (the list of file names) and "application/octet-stream" (the contents of the file). I suspect that Gimp is preferring the raw data over the file name for some reason. Probably, Thunar only offers the file name, which would explain why it works there.

    So, closing this on the assumption that it's a Gimp bug... (the comment there seems to indicate the same thing).

     

Log in to post a comment.