Support for Portable Devices

[admin]

Also, the issue mentioned by someone else a few pages back in this thread, about unlocking a connected device and seeing no automatic refresh, is still present in the latest builds.

2. No, I could not repro that.

I can reproduce this, but I'm pretty sure it works as expected since Suspend Auto-Refresh seems to be forced to enabled on Computer and within the portable device. Even in a fresh instance when I enable Auto-Refresh and Include Network locations and Include removable drives I cannot disable the suspension. Though this really confuses me since Computer does refresh for new drives even though it should be suspending auto-refresh.


One new discovery - XY will resume browsing a portable device which can adversely affect the startup time. This should instead show a message similar to network locations or searches.

XYplorer was closed with this tab pointing to a portable device.

Click the icon to browse the device now:
Path\On\Device

1. Thanks for mentioning this. XY's auto-refresh is fed by two totally different Windows mechanisms. Both are turned off when Auto-Refresh is turned off, but only one of them can be "suspended". PD locations can only be watched by the mechanism that cannot be suspended, so no suspend here. Next version fixes the double-bug: Suspend should be OFF and DISABLED.

2. I don't think this can ever be as bad as network. So it's okay as it is.

[TheQwerty]

1. ... Next version fixes the double-bug: Suspend should be OFF and DISABLED.

Then I might consider it a bug that XY does not refresh as WE does when the device is unlocked and thus starts sharing its contents. Will try in next version before deciding.

2. I don't think this can ever be as bad as network. So it's okay as it is.

Perhaps not but here it's bad enough to make you wonder if you actually started XY.

In a relatively fresh instance:
Loaded in: 7,875 ms at 2/10/2015 9:59:54 AM
Loaded in: 8,022 ms at 2/10/2015 10:00:48 AM
Loaded in: 8,010 ms at 2/10/2015 10:01:10 AM
vs
Loaded in: 744 ms at 2/10/2015 10:01:37 AM
Loaded in: 683 ms at 2/10/2015 10:01:55 AM
Loaded in: 675 ms at 2/10/2015 10:02:08 AM

[admin]

Hm, what device is that? I get about 750 msecs when I start on my tablet.

when the device is unlocked ...

Uh, unlocked ... looks as if did not read that bug report closely enough... ... where do you unlock a device??? and why?

[Filehero]

Also, the issue mentioned by someone else a few pages back in this thread, about unlocking a connected device and seeing no automatic refresh, .....

it was me (as Functional Improvement).

Uh, unlocked ... looks as if did not read that bug report closely enough... ... where do you unlock a device??? and why?

Usually it's the simple PIN. Unless it is entered MTP-access is impossible.

[TheQwerty]

Hm, what device is that? I get about 750 msecs when I start on my tablet.

A Nexus 5.

when the device is unlocked ...

Uh, unlocked ... looks as if did not read that bug report closely enough... ... where do you unlock a device??? and why?

It's the screen lock which requires a PIN, pattern, or password (PPP) that you can set to "prevent" someone from actually using the device.

For Nexus/Android: https://support.google.com/nexus/answer/2819522?hl=en

In the case of a Nexus 5, if it is unlocked WE/XY show the content.
If it is locked and waiting for the PPP then it appears as empty.
Once unlocked WE refreshes automatically to show the contents, XY requires a manual refresh.

[admin]

Ah, that one. I don't have such devices...

Please help me to find out of there is a Windows message connected to this unlocking. Run this thru AB, then unlock the device.

Code: Select all

logchange 1;

[TheQwerty]

After unlocking:

HandleShellNotifyEx 1000: SHCNE_UPDATEDIR
Path1:
File1: Nexus 5
Path2:
File2:

EDIT:

10:41:50.709 >> ShellNotify: SHCNE_UPDATEDIR: | Computer > |
10:41:50.803 >> ShellNotify: SHCNE_UPDATEDIR: | Sync Center > |
10:41:54.330 >> ShellNotify: SHCNE_DRIVEREMOVED: | Internal storage > |
10:42:10.985 >> ShellNotify: SHCNE_UPDATEDIR: | Nexus 5 > |

Plugging in, browsing to Nexus 5 (while locked), unlocking, manual refresh (F5).

EDIT 2: I think that SHCNE_DRIVEREMOVED may have been unrelated to the experiment at hand as I do not see it consistently.

[admin]

Thanks! Might work better in next beta.

[admin]

Hm, what device is that? I get about 750 msecs when I start on my tablet.

A Nexus 5.

Okay, maybe in PD 2.0. This is a bit of work to get right.

BTW, we are close to Carnival here in Cologne (which also made me delay 15.00) -- a very bad time to suggest new features.

[TheQwerty]

Hm, what device is that? I get about 750 msecs when I start on my tablet.

A Nexus 5.

Okay, maybe in PD 2.0. This is a bit of work to get right.

BTW, we are close to Carnival here in Cologne (which also made me delay 15.00) -- a very bad time to suggest new features.

To be honest I don't actually care whether you prevent browsing PDs on startup or not. The only time I've ever browsed a PD in the last 5 years is to test XY's support for PD.

I no longer tolerate tethering devices via wires.

[Shadow]

[FlameArrester] I read back through most posts and did not see this discussed, but I may have missed it.[/FlameArrester]

When in a portable device folder, double-clicking on a file gives a 'The system cannot find file specified' error.

dc.jpg (72.4 KiB) Viewed 2602 times

but right-clicking brings up the context menu, and executing an option there does function properly.

rc.jpg (69.22 KiB) Viewed 2602 times

WE does successfully launch the associated default program on double-clicking a file.

v14.80.0229
win8.1/64

[TheQwerty]

When in a portable device folder, double-clicking on a file gives a 'The system cannot find file specified' error.

http://www.xyplorer.com/xyfc/viewtopic. ... 40#p117740
If that list is still correct (and I think it is) then opening is not yet supported and is not planned for v1 of PD support.

[admin]

[FlameArrester] I read back through most posts and did not see this discussed, but I may have missed it.[/FlameArrester]

When in a portable device folder, double-clicking on a file gives a 'The system cannot find file specified' error.

dc.jpg

but right-clicking brings up the context menu, and executing an option there does function properly.

rc.jpg

WE does successfully launch the associated default program on double-clicking a file.

v14.80.0229
win8.1/64

Funnily your post inspired me to see the solution! Next version *might* support the dbl-click. It works fine here (Win8.1).

[Filehero]

2) Turn off auto-refresh. Does F5 crash it then?

Nope, then I can't provoke any crashes. However, with auto-refresh on it still crashes with 14.80.0229

Good
Auto-refresh on Unlock now works.

Hmmm
Auto-refresh on plug-in/off still doesn't work.
In either plug cases I mostly see a

Code: Select all

  HandleShellNotifyEx 1000: SHCNE_UPDATEDIR
  Path1: 
  File1: MyPC
  Path2: 
  File2:

whereby I don't get why the trigger apparently is "MyPC" (though that's the focused tree node)

During my plugging cycles I encountered exactly once

Code: Select all

  HandleShellNotifyEx 80: SHCNE_DRIVEREMOVED
  Path1: 
  File1: my830
  Path2: 
  File2: 

FH

[Filehero]

Hi Don,

no, I don't intent to haunt you, but with

Code: Select all

v14.80.0230 - 2015-02-10 21:30
    + Portable Devices: Now you can open some items by dbl-click. Images,
      e.g., should be opened by the Windows Preview. Others, like text files,
      will probably not work. Explorer appears to open a temporary copy of them,
      but XY does not go this way.
     ...
    ! Portable Devices: Auto-Refresh cannot be suspended on PDs so View |
      Suspend Auto-Refresh should be OFF and DISABLED for them. Done.

the fist 5 trials XY crashed immediately upon unplug. Even a freshed XY was killed.

After some XY restarts and minutes later it didn't happen anymore, just to reappear again with the next test. Feels a bit like a sort of weird timing issue.

Anyway, I leave it for tonight.

Hats off for your enduring patience.

FH