Preview Window offsets for PDFs

[Magnus]

When I preview PDFs (Foxit Reader default) the right "half" of the documents is displayed (png, jpg display correctly).


You can see how the preview scrollbar has moved away from the window edge.

This is on Win11x64, using a 64-bit preview dll from Foxit.

Any ideas on how to fix this? Thanks!

[Magnus]

So no thoughts here?

[Norn]

That's a wish? Ctrl+F8...

[highend]

Does it happen with a fresh XY instance as well?

Execute this via the address bar to get one
::fresh;

There was a similar issue here:
viewtopic.php?f=3&t=23317

Don't know what actually solved it...

[Jack]

Seems like this issue dates back quite a ways. It can't be all that common since it isn't generating many posts.

Am I correct in thinking that for some unknown reason it sometimes just goes away ? 'Fresh start' btw did nothing here.

I'm guessing it is unfixed? I checked the bug post (if it looks like a bug and acts like a bug) but a 'preview pane position' search turned up nothing and 'preview pane' turned too much too sift through.

[TheQwerty]

FWIW, I'm using PDF X-Change and have noticed similar strangeness in the viewing area for previews - especially between the preview pane and the Info Panel preview tab.
It seems to occur more frequently with Use 64-bit preview handlers for preview enabled, but even with the 32-bit handler the Info Panel preview seems to think the viewing area is wider than the tab's width at times.

Here's the help PDF supposedly zoom to Fit Width:

20220411-145153.png (72.64 KiB) Viewed 3879 times

Unfortunately, I haven't been able to wrap my head around what might be happening so I have nothing more than another data point to add.

[iamseoul]

viewtopic.php?f=3&t=23918&start=15

I'll solve it on page 2
If I turn off the 64-bit preview handler in the latest version, I can see it properly
Untick Configuration | Other | Shell Integration | 64-bit Windows | Use 64-bit preview handlers for preview.

[TheQwerty]

Thanks, iamseoul - I'm familiar with that setting, but as I mentioned in my post there still seems to be issues with the 32-bit handler in the Info Panel getting the wrong sizing.

It's much better than the issues with the 64-bit handler but still an issue.

[Jack]

Thanks iamseoul and TheQwerty it seems some progress is being made. Alas no change here.

To add another bit of information, here is a really odd happenstance of what happens when trying to preview an odt file

[Horst]

What preview handler do you have for odt files ?

[Jack]

Good suggestion.

odt is listed as one of the file extensions that are handled under 'Office Files;' this is as shipped. Otherwise, regarding what facility xy is itself using to do the previewing, that I don't know.

[TheQwerty]

regarding what facility xy is itself using to do the previewing, that I don't know.

Running this script will display information about what handler ("facility") XY is currently using to preview:

Code: Select all

::text get('PreviewHandler');

For instance, here's what I get:

GUID: {84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}
DefaultName: Microsoft Word previewer
DisplayName: @C:\Program Files\Microsoft Office\Root\VFS\ProgramFilesCommonX64\Microsoft Shared\Office16\oregres.dll,-487

FriendlyTypeName: @%ProgramFiles%\Windows NT\Accessories\WORDPAD.EXE,-301

I don't have any odt files to test and the one I quickly created in Word results in a 'Cannot Preview' in XY although it works in WE.

EDIT: Changed the script to get the handler currently in use by preview.

[highend]

results in a 'Cannot Preview' in XY although it works in WE

Try to uncheck the odt entry in "Office" and add a user defined entry that includes the bitness:

Code: Select all

odt>{84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}>64

[TheQwerty]

That seems to work here - thanks highend!

But I'm a very confused why that works when I tried with Use 64-bit preview handlers for preview both enabled and disabled and fallback disabled to simplify the logic.


EDIT: Heck why does the get script I posted display the same exact thing no matter what the 64-bit setting is or if a custom handler is defined?
Does it only report on what's registered and not what XY is doing?

EDIT 2: Because I'm an idiot who didn't RTFM:

Omit the extension parameter to learn about the currently active preview handler while a preview is being shown.

[highend]

It seems to be an oddity with 64-bit Office installations. It's exactly the same for the msg extension.