Hi,
I wonder if you could make this functionality better?
If the wallpaper image is from a folder with a very large number of images in it, the selected image is often not in the opening windows view and you cannot identify what the selected image is. Scrolling the windows seems to lose focus on the image as the thumbnail's re-render.
Pete

Yes Owen, will do when I get chance.
Pete

OK, Owen. So I just got set to do this today. I did a test first - right-clicked desktop wallpaper > Display Fusion > show wallpaper in Windows Explorer. Explorer window opened for folder with hundreds of photos in it. The window opened and scroll bar was fully at the top of the slider. The photo was well down and not selected\highlighted. When I manually scrolled to the photo location in the window it was not selected.
Next I repeated this time attempting to video, but every time the photo was correctly selected, and scroll was in correct location. Basically now after broken attempt I can't repeat it.
I don't have time to keep repeating this, just note it sometimes breaks. Hope you can find a breakage. Maybe I just have to try a second time to get it to work?
OK, I got it to break, and then then work. Unfortunately I only have stills. Both for same desktop image. Notice the scrollbar in broken image and then in ok image.
Pete

Owen, this is not fixed on the system I justed tested on. Win11 22621.1992 with 3 Dell monitors, 2 with wallpaper, 1 without. Opens the correct folder (as before) for the specific photo but does not select the image. If you need further info let me know. Some of my photo folders have 100's of images. I also have sort by date taken and ascending if that is useful.
Also to note in this beta, there is no icon for DF in context menu. I am running StartAllBack with W10 taskbar.

OK, so I have given it some time after the install of the beta and it seems better now. I will keep you posted.

Obviously context icon is still missing.

Yes desktop context menu. I am guessing this may be caused by StartAllBack as on another computer just running standard interface of W11 the DF icon is visable in the W11 context menu after going to show more options.
The below image is from system with StartAllBack:

Hi there,

This issue still exists in the current beta. I'm using DisplayFusion Pro 11.0 (Beta 2) on Windows 11 (23H2) [22631.3447].

Selecting 'Open Wallpaper Image in File Explorer' SOMETIMES works, but usually does not. What it does is open the folder where the image is located, but does not select the image and stays at the top of the folder items list. If I leave the folder open on my desktop, and then select the DF menu item again, it will then (in the same folder window) highlight the image as expected during the first attempt. If I close the Windows Explorer folder, and then select the menu item, it still does not work. I have to select the menu item with the folder open for the 2nd attempt to work.

This is an issue, as sometimes the wallpaper is in the process of changing while you are trying to select the menu item, which then causes it to potentially select the wrong image in the folder.

Sorry to re-open an old issue, but I thought it might make sense if the issue that was fixed is broken again in the same place.

Thanks!

I am not really sure it was ever properly fixed; it may have improved - sometimes it selects the image and others not. I am not sure what causes the different results.

@Owen Muhlethaler:

Any chance you guys can look into this, please?

I'm pulling from various OneDrive folders that are sync'd to the computer (so local).

So I have similar configuration - photos in Onedrive folders that are synced locally.
But DF picking correct images works now about 65% of the time.

Awesome, thank you!

Hi there,

Any progress with this issue?

Thanks!

Owen,
On my first attempt with new beta it is doing the same.
On first attempt to open an image in explorer the correct folder opens but with no image selected.
If I immediately do it again after closing the window it slects the correct image.
These are images in sub folders withing Ondrive, but that are "always kept on the device".

It's better than before, but still doing the same thing every now and then.

Obviously I don't know the coding behind this but I would think from a users perspective you would want the folder where the image is located opened up first, then perform a slight delay, and then select the image. The way it's doing it right now when it doesn't work seems to be that the folder takes longer to open up (probably due to the number of images it contains) and the image selection routine might be happening before the folder 'finishes' opening (thumbnails take time,etc). Of course I could be wrong in the logic behind that.

I should note that my folder with images is set to display thumbnails, and not a file listing, or details view, so that it's easy to visually identify the image right in the Explorer view, rather than having to manually open it in a viewer app that is installed on the system. Hence there could be an additional delay to 'finish' opening the folder as there are a lot of images (we're talking 1000+) with the folder set to 'thumbnail' view. If there could be a verification of some kind to say that the folder has completed loading it's view to the user before automatically selecting the image, that would help I would think.

When it's not working properly, I notice that if I leave the folder with the thumbnails open, and then click on the context-menu item to open the wallpaper a second time, it uses the same folder window it had just opened, but will then select the correct image. However, if I CLOSE the folder and perform the context menu click a second time, it has the same problem where the folder opens up, but the image is not selected. This behaviour leads me to believe there is an issue with the speed in which the folder opens, and the speed in which the process that selects the image happens. Essentially, the 2nd part (the image selection portion) happens too quickly, occurring before the folder has 'finished' loading. This may be dependent on the OS doing multiple things at the same time, or just generally the load on the system at the time of the request to load the image causes enough of a delay that the 2nd step happens before the 1st step has completed. Again, I think if a verification of the folder 'finished' loading could be put into that process before the image selection step happens, it would work correctly every time.

Hope that helps you guys catch the root cause!

I have now tested this on a few systems and if anything is seems worse now than before. It more often that not does not select the image at all. Correctly opens the correct folder but does not select the correct image.

Could it be made into 2 API calls, with a delay in between? Not a programmer here, but trying to help with a solution.