PDF Explorer > General

InfoEdit field shortcut key

<< < (3/3)

RTT:

--- Quote from: Padanges on August 19, 2016, 08:33:30 AM ---Any idea when it would be possible to check the updated workflow with these changes? My Trial version time is running down ;D and I still have some features to test, check reactions to DB changes, verify couple bugs, and to code some ideas for tools.

--- End quote ---
No idea right now. Still some things to do.
If you propose any type of collaboration, that adds value to the project and I agree to accept, I will be pleased to offer you a free license. Just email me and let me know.


--- Quote ---Well, to set focus on DiskTree you have to select it and that requires you to drag the mouse... But once you are near the selected folder it is enough to re-click it and the refresh function kicks-in so there not much of a use for a shortcut which requires mouse where the mouse use can do the job. Without the Focus F5 shoots you up to the Images mode. Hence, it would be handy if F5 would refresh the "DiskTee".

--- End quote ---
It also refreshes the tree, don't just initiate a new scan. But yea, the F5 should be global to the PDFInfo tab. I just added it later, and the F5 was already taken by the extract images so decided to not mess with it.


--- Quote ---
--- Quote ---I can have a grid layout with only standard fields and the InfoEdit tool is still visible, as long the layout includes, at least, an editable field when the "hide invisible fields from the rest of the interface" option is also selected. With what fields list are you getting this erroneous behavior?
--- End quote ---
To get the trick: create a new Grid Layout with let's say Filename and Size, then check "hide invisible fields from the rest of the interface" and restart PDFe.
Now that you have mentioned "hide invisible fields from the rest of the interface" option, I get the idea why it happens so. This could be considered as a minor bug, I guess, from the new user's perspective.

--- End quote ---
Instead of hidden it can be set disabled, when there are not editable fields. Maybe with a text line message stating that fact?

RTT:

--- Quote from: Padanges on August 19, 2016, 08:37:15 AM ---
--- Quote ---One of the big problems of this specific functionality shortcuts is that the PDF readers steal the focus from the main application and there is no easy way to handle this (at least I've not found a good one) and this shortcuts workflow gets easily broken when the reader is loaded with a new file.
--- End quote ---

As far as I have tested, ctrl+up or ctrl+down always works and does not get forwarded to Internal PDF Reader - so everything should be OK using that scheme. But I guess you can always steal (back) focus by making a false ALT keypress (and cancelling it) which is handled by PDFe.

--- End quote ---
These specific shortcuts are being delivered by a global keyboard hook. It's the only way I know to work it when these ActiveX embedded controls are focused and also process the same hotkeys. I suppose a globally hooked shortcut to get the focus back to PDFE is also a possibility. :-\
Does the ALT keypress trick you propose really gets the focus back to PDFE, or I'm missing something? The main menu appears to get the focus but in reality PDFE is still not accepting any other keys. At least in Windows 10. I've not tested in other Win versions.

Padanges:

--- Quote ---If you propose any type of collaboration, that adds value to the project and I agree to accept
--- End quote ---

I believe we are collaborating already :) but I will check if there's anything of greater value I could offer.


--- Quote ---I just added it later, and the F5 was already taken by the extract images so decided to not mess with it.
--- End quote ---

Well, then you could give us an option to remap it using shortcut preferences.


--- Quote ---Instead of hidden it can be set disabled, when there are not editable fields. Maybe with a text line message stating that fact?
--- End quote ---

I think it's a minor issue which gets in a way only once you start exploring PDFe properties but seeing it disabled instead of trying to figure out why it disappeared would be a better choice, in my opinion.


--- Quote ---Does the ALT keypress trick you propose really gets the focus back to PDFE, or I'm missing something?
--- End quote ---

Actually, both the internal viewer and PDFe starts responding after the ALT keypress. But it is still ambiguous how it responds because I've noticed couple times other reactions. So I guess it doesn't help much.
Have you tried to disable the viewer control while it is loading (set component property to disabled), then on click or a timer to enable it so it would get back as focusable? This might work. Maybe it is possible to do the same trick with each keypress, so that you could capture them with PDFe?

RTT:

--- Quote from: Padanges on August 22, 2016, 11:52:02 AM ---Actually, both the internal viewer and PDFe starts responding after the ALT keypress. But it is still ambiguous how it responds because I've noticed couple times other reactions. So I guess it doesn't help much.

--- End quote ---
I've now added some code to get focus back to PDFE when the main menu gets active, so the ALT key can now reliably be used to do that. Still not the best solution.

--- Quote ---Have you tried to disable the viewer control while it is loading (set component property to disabled), then on click or a timer to enable it so it would get back as focusable? This might work. Maybe it is possible to do the same trick with each keypress, so that you could capture them with PDFe?

--- End quote ---
The problem is that the user might indeed want to get the reader focused, just after document is loaded, so it can changes pages, etc.
The alt key trick is working now, and leaving the mouse pointer over the grid worked since ever. Probably a globally hooked hotkey, specific to get the focus back to PDFE, is the way to go. The alt key trick needs two clicks, one to get the focus and another to exit the menu and get back the focus to the previously focused control.

Navigation

[0] Message Index

[*] Previous page