<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Embarassing that I did not think of that - I almost never use a file
    manager, but still. Thanks for your guidance.<br>
    Is it ok if I open a bug report (wishlist) asking for such a
    rewrite, even though this is understandably not a priority? Just to
    have something to refer to on the debian bugtracker.<br>
    <br>
    <div class="moz-cite-prefix">On 18/12/16 13:38, Gilles Caulier
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAHFG6sEooifZDKUYjBCP1q+WtDx8iZLP6TGfWwPA5DeNdZykbg@mail.gmail.com"
      type="cite">
      <div dir="ltr">use Dolphin file manager and D&D file from DK
        to target in Dolphin.
        <div><br>
        </div>
        <div>The tool must be re-written in fact.</div>
        <div><br>
        </div>
        <div>Gilles Caulier</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2016-12-18 13:37 GMT+01:00 Simon Frei <span
            dir="ltr"><<a moz-do-not-send="true"
              href="mailto:freisim93@gmail.com" target="_blank">freisim93@gmail.com</a>></span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> Ok, so if I
              understand you correctly this tool is just kept for legacy
              reasons but might even be completely removed in the
              future?<br>
              Is there a way to copy files from digikam to some path
              that is not part of any collection? For me this is an
              important feature (e.g. to copy a specific selection of
              pictures using tags/filters to a usb stick for
              presentation on a different computer).
              <div>
                <div class="h5"><br>
                  <br>
                  <div class="m_7232700737709813954moz-cite-prefix">On
                    18/12/16 13:02, Gilles Caulier wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">It miss in AppImage because it use
                      KIO which use a lots of run time dependencies not
                      solvable with AppImage. Also, KIO do not work
                      under OSX and Windows. So, for me there is no
                      future of KIO in digiKam. digiKam will become more
                      and more a pure Qt application.
                      <div><br>
                      </div>
                      <div>Typically, we drop all KIO dependencies in
                        digiKam & co excepted this one. We don't
                        have planed to port this tool as pure Qt5
                        implementation.</div>
                      <div><br>
                      </div>
                      <div>Do no ask me which run time dependency is
                        missing. KIO is a waste of time to work
                        properly. I lost more weeks to try to bundle
                        this tool in all digiKam bundles.</div>
                      <div><br>
                      </div>
                      <div>Gilles Caulier</div>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">2016-12-18 12:27
                        GMT+01:00 Simon Frei <span dir="ltr"><<a
                            moz-do-not-send="true"
                            href="mailto:freisim93@gmail.com"
                            target="_blank">freisim93@gmail.com</a>></span>:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          <div bgcolor="#FFFFFF" text="#000000"> Hi<br>
                            <br>
                            When I use debian packages or compile
                            digikam myself, it freezes when on clicking
                            "Select target location..." in the "Export o
                            Remote Storage" dialog. The message on the
                            console is GLib/Gdk related, so I assumed it
                            is a debian dependency issue. I tried to
                            verify this by using the appimage
                            (5.4.0-01), but there is no "Export to
                            remote storage..." entry in the "Export"
                            menu there. So what is the status of that
                            tool, i.e. why is it missing in the
                            appimage?<br>
                            <br>
                            For reference this is the command line
                            output on freeze:<br>
                            <pre class="m_7232700737709813954m_5190885071840054351message">(digikam:2410): GLib-GObject-WARNING **: cannot register existing type
'GdkWindow'

(digikam:2410): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0'
failed

(digikam:2410): Gdk-CRITICAL **: gdk_window_ensure_native: assertion
'GDK_IS_WINDOW (window)' failed</pre>
                            and the backtrace: <a
                              moz-do-not-send="true"
                              class="m_7232700737709813954m_5190885071840054351moz-txt-link-freetext"
                              href="http://pastebin.com/xLSevGhy"
                              target="_blank">http://pastebin.com/xLSevGhy</a><br>
                            <br>
                            Cheers,<br>
                            Simon<br>
                          </div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>