Page 1 of 1
Run script from fp - Custom keyboard shortcuts
Posted: 12 Nov 2015 16:20
by highend
If "Advanced Options... - Allow Custom Keyboard Shortcuts in Preview"
is enabled, the F8 button uses the assigned keyboard shortcut from XY (in Fresh: Show Navigation Panels) instead.
Wouldn't it be better to override this specific hotkey when custom keyboard shortcuts is enabled?
Re: Run script from fp - Custom keyboard shortcuts
Posted: 12 Nov 2015 16:31
by admin
That would be an exception. Maybe a good one, not sure. I personally never use Allow Custom Keyboard Shortcuts in Preview.
Re: Run script from fp - Custom keyboard shortcuts
Posted: 12 Nov 2015 21:12
by highend
v15.90.0030 - 2015-11-12 20:54
! Floating Preview: "Run Script" did not work from the menu when "Allow
Custom Keyboard Shortcuts in Preview" was enabled. Fixed.
Still not working in a fresh; instance.
It doesn't execute "Show navigation panels" anymore (that's a fix) but it still doesn't execute the assigned button script...
Left clicking the button works, "Advanced Options... - Run script" works. F8 doesn't

Re: Run script from fp - Custom keyboard shortcuts
Posted: 12 Nov 2015 21:41
by admin
You mean if "Allow Custom Keyboard Shortcuts in Preview" is enabled? F8 is not supposed to work then. It should toggle navigation panels (it does not? that's a bug).
But generally, I currently think about having both sets of KS active in the FP always (and remove the option "Allow Custom Keyboard Shortcuts in Preview"), with priority to the FP's own set. All other KS would be handled by CKS definitions. Okay?
Re: Run script from fp - Custom keyboard shortcuts
Posted: 12 Nov 2015 22:03
by highend
You mean if "Allow Custom Keyboard Shortcuts in Preview" is enabled?
Yes
F8 is not supposed to work then. It should toggle navigation panels (it does not? that's a bug).
*laughs* That's the complete opposite of what I expected
But generally, I currently think about having both sets of KS active in the FP always (and remove the option "Allow Custom Keyboard Shortcuts in Preview"), with priority to the FP's own set. All other KS would be handled by CKS definitions. Okay?
That's the right way

"Floating Preview: New way to handle keys"
Posted: 17 Nov 2015 17:35
by ghost zero
v15.90.0031 - 2015-11-13 15:31
*** Floating Preview: New way to handle keys. Now Floating Preview keyboard
shortcuts and main window keyboard shortcuts (Custom Keyboard Shortcuts)
are always active in the Floating Preview, but Floating Preview keys have
priority. If a key combination does not trigger anything in the Floating
Preview then it's passed on to the main window.
Please add an option to turn this off. Because I don't want to risk accidently triggering an unknown function if I press a wrong hotkey in preview mode.
Re: "Floating Preview: New way to handle keys"
Posted: 17 Nov 2015 17:44
by admin
ghost zero wrote:
v15.90.0031 - 2015-11-13 15:31
*** Floating Preview: New way to handle keys. Now Floating Preview keyboard
shortcuts and main window keyboard shortcuts (Custom Keyboard Shortcuts)
are always active in the Floating Preview, but Floating Preview keys have
priority. If a key combination does not trigger anything in the Floating
Preview then it's passed on to the main window.
Please add an option to turn this off. Because I don't want to risk accidently triggering an unknown function if I press a wrong hotkey in preview mode.
Argh. Should have seen this coming.

So "Allow Custom Keyboard Shortcuts in Preview" will be back.

(Only that this time the FP keys will stay active.) Sigh.
Re: "Floating Preview: New way to handle keys"
Posted: 17 Nov 2015 17:50
by ghost zero
admin wrote:ghost zero wrote:
v15.90.0031 - 2015-11-13 15:31
*** Floating Preview: New way to handle keys. Now Floating Preview keyboard
shortcuts and main window keyboard shortcuts (Custom Keyboard Shortcuts)
are always active in the Floating Preview, but Floating Preview keys have
priority. If a key combination does not trigger anything in the Floating
Preview then it's passed on to the main window.
Please add an option to turn this off. Because I don't want to risk accidently triggering an unknown function if I press a wrong hotkey in preview mode.
Argh. Should have seen this coming.

So "Allow Custom Keyboard Shortcuts in Preview" will be back.

(Only that this time the FP keys will stay active.) Sigh.
thanks, and please also revert back to the previous behavior upon upgrade.