Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Drop uri from finder in 5.4 contains inode number instead of path
Forum Updated to NodeBB v4.3 + New Features

Drop uri from finder in 5.4 contains inode number instead of path

Scheduled Pinned Locked Moved General and Desktop
10 Posts 3 Posters 2.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    thomas_tw
    wrote on last edited by
    #1

    both drop.urls in qml and mimedata->urls() do return urls like this:
    file:///.file/id=6571367.17251089
    where the last number is the inode number and the first seems to be related to the device.
    in 5.3 the behaviour was to return the path:
    file:///Users/ttw/Desktop/test.mp4

    anyone having the same issue dropping a file/folder from the finder into a widget, qml application or the dropsite example?

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi and welcome to devnet,

      What version of OS X/XCode are you using ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • T Offline
        T Offline
        thomas_tw
        wrote on last edited by
        #3

        I'm using OS X 10.10.1 and Xcode 6.1.1. I don't notice any differences using qt5.3, so i was suspecting it's not related the OS-Version. Seems i was wrong. I did find this topic in the bugreports.
        https://bugreports.qt-project.org/browse/QTBUG-40449

        Thanks

        1 Reply Last reply
        0
        • P Offline
          P Offline
          patrickkidd
          wrote on last edited by
          #4

          Is there a workaround for this using Qt classes? I am using PyQt so don't have access to obj functions.

          Thanks!

          https://alaskafamilysystems.com/

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #5

            Hi,

            You'd better update the Qt version you are using through PyQt

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0
            • P Offline
              P Offline
              patrickkidd
              wrote on last edited by
              #6

              Has this been fixed? In which version of Qt? I read through the issue tracker and didn't see any resolution.

              https://alaskafamilysystems.com/

              1 Reply Last reply
              0
              • SGaistS Offline
                SGaistS Offline
                SGaist
                Lifetime Qt Champion
                wrote on last edited by
                #7

                The report currently states fixed for Qt 5.4.1

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                0
                • P Offline
                  P Offline
                  patrickkidd
                  wrote on last edited by
                  #8

                  ok great, thanks!

                  https://alaskafamilysystems.com/

                  1 Reply Last reply
                  0
                  • P Offline
                    P Offline
                    patrickkidd
                    wrote on last edited by
                    #9

                    Actually I almost downloaded qt-5.4.1 but then looked in the release notes and saw nothing for this bug. So I looked at the issue tracker again and saw that it is listed as affects 5.4.1 and then the fix version is also 5.4.1. Not sure what that means. And I still don't see a resolution in the comments.

                    Am I blind or is this is still broken!

                    https://alaskafamilysystems.com/

                    1 Reply Last reply
                    0
                    • P Offline
                      P Offline
                      patrickkidd
                      wrote on last edited by
                      #10

                      Or wait, it looks like 5.4.0 is the current release and 5.4.1 hasn't been released yet. It's probably reported as affecting 5.4.1 because it is still in progress.

                      Yes?

                      https://alaskafamilysystems.com/

                      1 Reply Last reply
                      0

                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups
                      • Search
                      • Get Qt Extensions
                      • Unsolved