Take note in the patch that the shortcuts for those are disabled. I only added
the text to the menu entry and removed the shortcut keys so all processing is
done in the key routine.So it shouldn't message with the Mac at all. I think
this should behave the same on Mac as it did before.
The Alt-menu is interesting....but I don't think Qt has a smooth way to do
that, do they?
de Mike W9MDB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Saturday, April 8, 2017 5:19 AM
Subject: Re: [wsjt-devel] F1/2/3 CTRL+M patch
On 08/04/2017 06:45, Black Michael wrote:
Allow F1,F2 and F3 to work when menus are hidden Change F1 to bring up local
help instead of online help Add CTRL+M text to menu entry without keyboard
shortcut to avoid hosing Macs Update tooltip for signal meter (had incorrect
info in it)
F1 right now brings up online help which seems like the wrong thing to do
IMHO. One may not have internet access and the local help is more up-to-date
anyways especially for dev versions.
I didn't see where the other function keys needed to be available when the
menus are hidden.
Hi Mike, I will try and look at this later. You are on dodgy ground with some
of this due to the way the Mac menus are expected to work. I like the idea of
using the ALT key to hide and show the menu bar and I had done some work to
implement this already but had not got it working to my satisfaction yet. This
mechanism is pretty common these days, for example many ribbon interface
Windows applications as well as Firefox and Thunderbird do it. Note that on Mac
and many Linux window managers and also the Ubuntu Unity desktop the menu is
more Mac like as a single shared system menu bar that cannot be hidden. I
believe the main issue is that we have introduced a binary feature (toggle)
that disables it's own enable switch, this is problematic as several users
appear to have turned in on "just to see what happens" and then have no idea
how to turn it back off. Splitting the menu bar hiding from the other control
hiding would seem wise if we can implement it without adding a lot of
complexity and future maintenance hazards.
BTW I believe that having F1 (CMD+F1 on Mac) show the online User Guide is
correct. We should not assume that the majority of users are using a
development build nor that the majority have no Internet connection. Having the
shortcut key go to the online documentation allows us to tweak the User Guide
post release and also to add foreign language translations which are selected
automatically according to the user's locale. The local User Guide should be
considered as a backstop for the very few that have no Internet connection and
a happy to have only a English version. If we do anything here then a warning
and reverting to the local User Guide if the online one cannot be fetched seems
appropriate if it is not too hard nor messy to implement.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
