Slight drawback when pinning "foxit reader". about pinwin

[rodribyte]

It is very useful for voice actors, so that they can read their lines while recording themselves. Many of them prefer simple applications. I am preparing a tutorial to show them.

[VictorZakharov]

@rodribyte Thanks for reporting it, I'll check when I have time.
Good to know that people are using my little tool in 2023.

[VictorZakharov]

@rodribyte I am able to reproduce the issue using the latest foxit reader.
Both CTRL + F11 and F12 work fine, and also after they were used, then clicking in tray and pinning using the mouse also works.

But initially clicking the tray icon to pin does not work with foxit. Ctrl F11/F12 should be identical to clicking from tray, so I don't have any immediate ideas on how to fix. I'll think about it, not a critical issue though.

I would assume everyone using hotkeys by now, I'd be surprised if clicking the tray icon is a common workflow for others.

[VictorZakharov]

Yeah, sorry @rodribyte, I will not be able to fix it. I looked at the code, both tray capture and hotkey capture have identical call stacks. And identical handles being captured. No idea why one works, but another one does not. I would need better understanding of Windows internals and a lot more time than I have on hand.

Also the issue has an easy workaround - using hotkeys instead of tray click. So using this workaround will be the resolution here.

[rodribyte]

It may be a windows problem, as deskpins also glitches a bit. But what would happen if clicking on the icon would call the shortcut (ctrl+f11) instead of the usual routine? El mar, 31 oct 2023 a las 20:54, Victor Zakharov ***@***.***>) escribió:

…

Yeah, sorry @rodribyte <https://github.com/rodribyte>, I will not be able to fix it. I looked at the code, both tray capture and hotkey capture have identical call stacks. And identical handles being captured. No idea why one works, but another one does not. I would need better understanding of Windows internals and a lot more time than I have on hand. Also the issue has an easy workaround - using hotkeys instead of tray click. So using this workaround will be the resolution here. — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDOXUWG3AYJORKF2KV2DUN3YCGFT7AVCNFSM6AAAAAA6WMRWYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBYGE4TAMBZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Rodrigo Saavedra Doblaje / Traducción y adaptación.

[VictorZakharov]

@rodribyte It calls the same function that CTRL+F11 calls. There is no difference in code.

Reacting to mouse click:

Using a hotkey:

BTW, foxit reader stopped pinning even with CTRL+F11. I suggest you report this issue to Foxit support and have them fix it. Especially since you found DeskPins also has issues pinning it.

[VictorZakharov]

@rodribyte DisplayFusion, the world's most popular multimonitor tool, has the same issue. It cannot pin Foxit Reader on top. So yes, definitely contact Foxit support and let them know. They need to fix it on their end.

[rodribyte]

Hello, how are you? I forgot to ask the creators of Foxit Reader directly, although the truth is that this has also happened to me with other software. But what I'm here to tell you is that I've been doing some tests and I realised that if I pin Foxit Reader, then unpin it, and then pin it again, the problem we mentioned before never occurs. Maybe you can use it to cheat the system. But you can check that when you have time, no rush on my part. Regards and thanks. El dom, 5 nov 2023 a las 8:05, Victor Zakharov ***@***.***>) escribió:

…

@rodribyte <https://github.com/rodribyte> DisplayFusion, the world's most popular multimonitor tool, has the same issue. It cannot pin Foxit Reader on top. So yes, definitely contact Foxit support and let them know. They need to fix it on their end. — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDOXUWC4FDJBNX5OHCOU6VLYC5QGTAVCNFSM6AAAAAA6WMRWYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTG4YDKMJUHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Rodrigo Saavedra Doblaje / Traducción y adaptación.

[VictorZakharov]

@rodribyte Yes, sorry, no time.