I'm using DOpus 12, Windows 10 and Office 2016, and my workflow really depends on using the preview pane in listers. And it works great, except I got a new 4k monitor and my regular human eyes forced me to set DPI scaling to 150%. And so problems happen.
Here's what previewing an Excel spreadsheet looks like at 100% scaling:
Changing the size of the window or the size of the viewer pane does affect the size of the spreadsheet preview, but it's still hovering outside of where it's supposed to be and too small. It's also smaller than you'd expect if it just didn't scale properly, so it's like something was divided by the scale factor instead of multiplied or whatever. It seems to be related to Office mostly. Here is a Word document doing the same thing:
Edit: For a little more completeness, Office previews do look (and scale) properly in Windows Explorer, and also all the other previews like images, text etc. look fine in DOpus. It seems it's only the Office preview handlers and DOpus that don't play well together.
That looks like a bug in the preview handler itself, possibly not taking account of the DPI of the host window.
I haven't seen that problem with the Office 365 preview handlers at 200% scaling, FWIW.
That's without using App-V. I don't know what App-V is to be honest; this is the first I've heard of it. As a virtualization technology of some kind it may complicate things. Could you tell me more about what it does and why it's involved with preview handlers?
Are you using mixed DPIs (different scaling factors on different monitors)? Or have you not rebooted after changing the DPI? Both can complicate things and expose bugs in various components and, unfortunately, Windows 10 itself
All the Office ones have the "App-V" label, and those are the ones causing the problem, whereas other handlers in the same plugin, like Foxit, work just fine. I'm also using Office 365, but as I understand it that's just the subscription plan, with 2016 being the version currently delivered to 365 users. Honestly I'm a little confused by the whole business model.
Anyway, if it works for you, perhaps you have different handlers installed than the ones shown above?
I appreciate you taking the time to look into this.
However, I spent a little time experimenting on my own, or rather many, many hours trying everything I could think of. Along the way I installed an old copy of Office 2007 Enterprise hoping I could use just the preview handler from that, I reinstalled Office 365 a bunch of times, I changed every DPI setting I could find, and much more.
Bottom line is, something I did seems to have fixed it. Previews are displaying correctly now, and everything is peachy. <3 Sadly I can't say what exactly did the trick, but I'm pretty confident that, even though this is a new installation of Windows 10 with pretty much default settings, whatever was wrong probably wasn't Directory Opus' fault.
So yeah, thanks again for your time. And I think you should remove the bug report tag, or close the bug ticket, or whatever you need to do.
I'm a long time user by the way, all the way back to the earlier Amiga versions. So additional thanks for an awesome file manager. Couldn't imagine my life without it. Only complaint is that I'd really like a Linux version too.
The "Microsoft App-V Preview handler for..." prefix on all their names is new to me, and suggests they're something different to the standard Office preview handlers.
With a normal, non-App-V install of Office the names would be thinks like "Microsoft Office" and "Microsoft Excel".
Yep. I'm back to only having Office 365 installed. I never saw an option for virtualization during installation, but whatever happened, here's what the plugin config window looks like now:
So App-V must somehow have been disabled (for preview handlers at least), and the scaling works. Seems very likely there's a connection there. Just for future reference if someone else runs into a similar problem.
