Re: [Kicad-developers] Zoom vs Help
Hi Garth, Thank you for the patch. I consider the changes to be low risk, so they have been committed in revision 5888. Regards, Orson On 07/04/2015 11:33 PM, Garth Corral wrote: On Jul 4, 2015, at 2:02 PM, Garth Corral gcor...@abode.commailto:gcor...@abode.com wrote: On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.commailto:stambau...@gmail.com wrote: On 7/1/2015 4:17 PM, Garth Corral wrote: The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. While I agree with you in principal, can you imagine what a mess our hot key definition code would look like if we had to avoid window manager key mappings for every Linux WM? Good luck with that. AFAIK, there is no wxWidgets code for determining WM key mapping so fixing the mapping at run time is also not likely. That being said, if you run into an issue, please send a patch with the requisite #ifdef/#endif wrapped OSX specific key mappings. So, any thoughts, OS X folks? It would be nice if the canvas switching had hotkeys that worked out of the box. Garth Here’s a patch to use Alt-F9,Alt-F11,Alt-F12 on OS X. Please apply if others agree. signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On 06 Jul 2015, at 17:37, Andy Peters de...@latke.net wrote: And replying to myself: Macs have the “fn” key which is just another modifier key. Its primary use is on laptop keyboards, where the top row Function keys have various defined uses such as display brightness, open Mission Control and Launchpad, audio volume up and down. By default, the function keys perform those “alternate” functions (which means they’re not really alternate, but …). That can be changed in the Keyboard Preferences (“Use All F1, F2, etc. keys as standard function keys”). How many users change that preference? I have no idea. But it might be worth mentioning this in the documentation somewhere in case a user starts banging on the keyboard saying “THIS DOESN’T WORK!” You probably can blame Apple for many things, but that “fn” behavior is definitely not Mac specific. My work laptop with Windows 7 behaves just the same way per default… Regards, Bernhard ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
Den 06/07/2015 17.37 skrev Andy Peters de...@latke.net: On Jul 6, 2015, at 8:17 AM, Andy Peters de...@latke.net wrote: On Jul 4, 2015, at 2:33 PM, Garth Corral gcor...@abode.com wrote: On Jul 4, 2015, at 2:02 PM, Garth Corral gcor...@abode.com wrote: On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote: On 7/1/2015 4:17 PM, Garth Corral wrote: The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. While I agree with you in principal, can you imagine what a mess our hot key definition code would look like if we had to avoid window manager key mappings for every Linux WM? Good luck with that. AFAIK, there is no wxWidgets code for determining WM key mapping so fixing the mapping at run time is also not likely. That being said, if you run into an issue, please send a patch with the requisite #ifdef/#endif wrapped OSX specific key mappings. So, any thoughts, OS X folks? It would be nice if the canvas switching had hotkeys that worked out of the box. Garth Here’s a patch to use Alt-F9,Alt-F11,Alt-F12 on OS X. Please apply if others agree. osx_canvas_hotkeys.patch Oh, those alt-keys are perfectly fine for me. And replying to myself: Macs have the “fn” key which is just another modifier key. Its primary use is on laptop keyboards, where the top row Function keys have various defined uses such as display brightness, open Mission Control and Launchpad, audio volume up and down. By default, the function keys perform those “alternate” functions (which means they’re not really alternate, but …). That can be changed in the Keyboard Preferences (“Use All F1, F2, etc. keys as standard function keys”). How many users change that preference? I have no idea. But it might be worth mentioning this in the documentation somewhere in case a user starts banging on the keyboard saying “THIS DOESN’T WORK! I am glad to help out with docs. If someone would be so kind as to point me in the right direction, I’ll do what I can. Please make a pull request at ciampix' kicad-doc repo on github. -a ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On Jul 6, 2015, at 8:17 AM, Andy Peters de...@latke.net wrote: On Jul 4, 2015, at 2:33 PM, Garth Corral gcor...@abode.com wrote: On Jul 4, 2015, at 2:02 PM, Garth Corral gcor...@abode.com wrote: On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote: On 7/1/2015 4:17 PM, Garth Corral wrote: The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. While I agree with you in principal, can you imagine what a mess our hot key definition code would look like if we had to avoid window manager key mappings for every Linux WM? Good luck with that. AFAIK, there is no wxWidgets code for determining WM key mapping so fixing the mapping at run time is also not likely. That being said, if you run into an issue, please send a patch with the requisite #ifdef/#endif wrapped OSX specific key mappings. So, any thoughts, OS X folks? It would be nice if the canvas switching had hotkeys that worked out of the box. Garth Here’s a patch to use Alt-F9,Alt-F11,Alt-F12 on OS X. Please apply if others agree. osx_canvas_hotkeys.patch Oh, those alt-keys are perfectly fine for me. And replying to myself: Macs have the “fn” key which is just another modifier key. Its primary use is on laptop keyboards, where the top row Function keys have various defined uses such as display brightness, open Mission Control and Launchpad, audio volume up and down. By default, the function keys perform those “alternate” functions (which means they’re not really alternate, but …). That can be changed in the Keyboard Preferences (“Use All F1, F2, etc. keys as standard function keys”). How many users change that preference? I have no idea. But it might be worth mentioning this in the documentation somewhere in case a user starts banging on the keyboard saying “THIS DOESN’T WORK! I am glad to help out with docs. If someone would be so kind as to point me in the right direction, I’ll do what I can. -a ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On Jul 4, 2015, at 2:33 PM, Garth Corral gcor...@abode.com wrote: On Jul 4, 2015, at 2:02 PM, Garth Corral gcor...@abode.com wrote: On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote: On 7/1/2015 4:17 PM, Garth Corral wrote: The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. While I agree with you in principal, can you imagine what a mess our hot key definition code would look like if we had to avoid window manager key mappings for every Linux WM? Good luck with that. AFAIK, there is no wxWidgets code for determining WM key mapping so fixing the mapping at run time is also not likely. That being said, if you run into an issue, please send a patch with the requisite #ifdef/#endif wrapped OSX specific key mappings. So, any thoughts, OS X folks? It would be nice if the canvas switching had hotkeys that worked out of the box. Garth Here’s a patch to use Alt-F9,Alt-F11,Alt-F12 on OS X. Please apply if others agree. osx_canvas_hotkeys.patch Oh, those alt-keys are perfectly fine for me. -a ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote: On 7/1/2015 4:17 PM, Garth Corral wrote: The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. While I agree with you in principal, can you imagine what a mess our hot key definition code would look like if we had to avoid window manager key mappings for every Linux WM? Good luck with that. AFAIK, there is no wxWidgets code for determining WM key mapping so fixing the mapping at run time is also not likely. That being said, if you run into an issue, please send a patch with the requisite #ifdef/#endif wrapped OSX specific key mappings. So, any thoughts, OS X folks? It would be nice if the canvas switching had hotkeys that worked out of the box. Garth smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On Jul 4, 2015, at 2:02 PM, Garth Corral gcor...@abode.com wrote:On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote:On 7/1/2015 4:17 PM, Garth Corral wrote:The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around.As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box.While I agree with you in principal, can you imagine what a mess our hotkey definition code would look like if we had to avoid window managerkey mappings for every Linux WM? Good luck with that. AFAIK, there isno wxWidgets code for determining WM key mapping so fixing the mappingat run time is also not likely. That being said, if you run into anissue, please send a patch with the requisite #ifdef/#endif wrapped OSXspecific key mappings.So, any thoughts, OS X folks? It would be nice if the canvas switching had hotkeys that worked out of the box.GarthHere’s a patch to use Alt-F9,Alt-F11,Alt-F12 on OS X. Please apply if others agree. osx_canvas_hotkeys.patch Description: Binary data smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
While we’re on the topic. There are other places where hotkeys are less than optimal on OS X. For example, F11 and F12 are taken for OS functions and never reach kicad, so selecting the canvases has to be done through the menus. Conversely, Cmd-C in kicad launches the calculator, so you can’t copy from the python console. These are just a couple I’ve noticed recently, I’m sure there are many more such issues. Garth On Jul 1, 2015, at 10:45 AM, Jean-Paul Louis lou...@yahoo.com wrote: Jean-Pierre, With OS X (Yosemite 10.10.4), Ctrl-F1 does not do anything while in any of Kicad apps. As Simon and Andy pointed out, the Mac OS X users are second class citizens, because most of the keys listed do not work as shown. Could we fix this before the stable release? Best regards, Jean-Paul AC9GH See below what we get in Kicad Manager: PastedGraphic-1.png Only the “?” has the expected effect. So this popup should be updated for OS X users by replacing the “Ctrl” by “Cmd”. in “eeschema”(Left) and Part Library Editor (Right), we get: PastedGraphic-2.pngPastedGraphic-3.png in “pcbnew”, we get: PastedGraphic-4.pngPastedGraphic-5.png On Jul 1, 2015, at 3:33 AM, jp charras jp.char...@wanadoo.fr mailto:jp.char...@wanadoo.fr wrote: Le 01/07/2015 02:37, Simon Richter a écrit : Hi, I've just tried to get context sensitive help using the F1 key, and found that instead it zoomed in. The menu claims that the hotkey for zooming in is Alt-F1, while the hotkey list accessible with the '?' key lists F1 without qualifiers. On Mac, Ctrl-'+' is used instead, which is fairly common in PC software as well these days (IE and Firefox, for example). Would it make sense to offer Ctrl-'+' and Ctrl-'-' on all platforms? Would it make sense to reserve F1 for context help? Simon Why to change? You can use Ctrl+F1 for help. Zooming is more frequently used than help, therefore using one key to zoom and 2 keys to call help is not bad. This is a basic optimization. For zoom, Alt-F1 and F1 are *not* equivalent. This is a remark which was made many times. F1 centers the screen to the mouse cursor, Alt-F1 does not. To be able to use the same key, you have to find a reliable way to know if a command comes from an accelerator key (you can use the mouse cursor position) or a menu activation (you cannot uses this position). (I do not yet found this way) There are many other commands like that. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
Le 01/07/2015 20:38, Garth Corral a écrit : While we’re on the topic. There are other places where hotkeys are less than optimal on OS X. For example, F11 and F12 are taken for OS functions and never reach kicad, so selecting the canvases has to be done through the menus. Conversely, Cmd-C in kicad launches the calculator, so you can’t copy from the python console. These are just a couple I’ve noticed recently, I’m sure there are many more such issues. Garth I am thinking you are confused by wxWidgets issues and Kicad issues. The mere fact you cannot copy using Cmd-C from the python console is a curious wxWidgets bug (specific to OSX) (looks like accelerator keys are captured by the wrong window, and not sent to the window which has the focus). On all systems or window managers, some keys are captured by the window manager and cannot be used as user commands (for instance F10 on Windows). Many keys using Alt modifier cannot be freely used as hotkeys (they do not work, or they are captured by the window manager). All hotkeys are configurable by user, so when a key is not working on a given window manager, you can easily remap it. The issue relative to Ctrl / Cmd is not clear for me. Is it just the name Ctrl which should be displayed Cmd (which is rather easy to change) or is it something else ? -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On Jul 1, 2015, at 12:22 PM, jp charras jp.char...@wanadoo.fr wrote: Le 01/07/2015 20:38, Garth Corral a écrit : While we’re on the topic. There are other places where hotkeys are less than optimal on OS X. For example, F11 and F12 are taken for OS functions and never reach kicad, so selecting the canvases has to be done through the menus. Conversely, Cmd-C in kicad launches the calculator, so you can’t copy from the python console. These are just a couple I’ve noticed recently, I’m sure there are many more such issues. Garth snip The issue relative to Ctrl / Cmd is not clear for me. Is it just the name Ctrl which should be displayed Cmd (which is rather easy to change) or is it something else ? I think you are correct that it is merely an issue with the display of hotkeys in the list and not an issue in the definition of the keys. Garth -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. Garth On Jul 1, 2015, at 12:22 PM, jp charras jp.char...@wanadoo.fr wrote: Le 01/07/2015 20:38, Garth Corral a écrit : While we’re on the topic. There are other places where hotkeys are less than optimal on OS X. For example, F11 and F12 are taken for OS functions and never reach kicad, so selecting the canvases has to be done through the menus. Conversely, Cmd-C in kicad launches the calculator, so you can’t copy from the python console. These are just a couple I’ve noticed recently, I’m sure there are many more such issues. Garth I am thinking you are confused by wxWidgets issues and Kicad issues. The mere fact you cannot copy using Cmd-C from the python console is a curious wxWidgets bug (specific to OSX) (looks like accelerator keys are captured by the wrong window, and not sent to the window which has the focus). On all systems or window managers, some keys are captured by the window manager and cannot be used as user commands (for instance F10 on Windows). Many keys using Alt modifier cannot be freely used as hotkeys (they do not work, or they are captured by the window manager). All hotkeys are configurable by user, so when a key is not working on a given window manager, you can easily remap it. The issue relative to Ctrl / Cmd is not clear for me. Is it just the name Ctrl which should be displayed Cmd (which is rather easy to change) or is it something else ? -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On 7/1/2015 4:17 PM, Garth Corral wrote: The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad where OS X specific issues must be worked around. As for the window manager capturing the functions keys, yes, that is what I said. The fact that F10 was skipped for canvas switching means that kicad is catering to a specific platform. I’m not likely to switch window managers on OS X, nor are other OS X users. Yes we could remap our keys but why should we? This should work out of the box. While I agree with you in principal, can you imagine what a mess our hot key definition code would look like if we had to avoid window manager key mappings for every Linux WM? Good luck with that. AFAIK, there is no wxWidgets code for determining WM key mapping so fixing the mapping at run time is also not likely. That being said, if you run into an issue, please send a patch with the requisite #ifdef/#endif wrapped OSX specific key mappings. Garth On Jul 1, 2015, at 12:22 PM, jp charras jp.char...@wanadoo.fr wrote: Le 01/07/2015 20:38, Garth Corral a écrit : While we’re on the topic. There are other places where hotkeys are less than optimal on OS X. For example, F11 and F12 are taken for OS functions and never reach kicad, so selecting the canvases has to be done through the menus. Conversely, Cmd-C in kicad launches the calculator, so you can’t copy from the python console. These are just a couple I’ve noticed recently, I’m sure there are many more such issues. Garth I am thinking you are confused by wxWidgets issues and Kicad issues. The mere fact you cannot copy using Cmd-C from the python console is a curious wxWidgets bug (specific to OSX) (looks like accelerator keys are captured by the wrong window, and not sent to the window which has the focus). On all systems or window managers, some keys are captured by the window manager and cannot be used as user commands (for instance F10 on Windows). Many keys using Alt modifier cannot be freely used as hotkeys (they do not work, or they are captured by the window manager). All hotkeys are configurable by user, so when a key is not working on a given window manager, you can easily remap it. The issue relative to Ctrl / Cmd is not clear for me. Is it just the name Ctrl which should be displayed Cmd (which is rather easy to change) or is it something else ? -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On Jun 30, 2015, at 10:56 PM, Garth Corral gcor...@abode.com wrote: On top of that, the hotkeys list is mostly wrong on OS X in that it shows Ctrl- as the modifier key when in fact it is Cmd- on OS X. This is indeed correct. In the standard Mac GUI (going back to before OS X), most of the CUI key combinations use the command key, not control. Mac users expect Cmd-S to be the “save” command, not Ctrl-S. But there’s no standard for non-standard (Application-specific) commands, so being explicit about Ctrl vs Cmd is necessary. -a ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
Le 01/07/2015 02:37, Simon Richter a écrit : Hi, I've just tried to get context sensitive help using the F1 key, and found that instead it zoomed in. The menu claims that the hotkey for zooming in is Alt-F1, while the hotkey list accessible with the '?' key lists F1 without qualifiers. On Mac, Ctrl-'+' is used instead, which is fairly common in PC software as well these days (IE and Firefox, for example). Would it make sense to offer Ctrl-'+' and Ctrl-'-' on all platforms? Would it make sense to reserve F1 for context help? Simon Why to change? You can use Ctrl+F1 for help. Zooming is more frequently used than help, therefore using one key to zoom and 2 keys to call help is not bad. This is a basic optimization. For zoom, Alt-F1 and F1 are *not* equivalent. This is a remark which was made many times. F1 centers the screen to the mouse cursor, Alt-F1 does not. To be able to use the same key, you have to find a reliable way to know if a command comes from an accelerator key (you can use the mouse cursor position) or a menu activation (you cannot uses this position). (I do not yet found this way) There are many other commands like that. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Zoom vs Help
Hi, I've just tried to get context sensitive help using the F1 key, and found that instead it zoomed in. The menu claims that the hotkey for zooming in is Alt-F1, while the hotkey list accessible with the '?' key lists F1 without qualifiers. On Mac, Ctrl-'+' is used instead, which is fairly common in PC software as well these days (IE and Firefox, for example). Would it make sense to offer Ctrl-'+' and Ctrl-'-' on all platforms? Would it make sense to reserve F1 for context help? Simon signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On a side note: Please note that the right click context menu shows the correct (without alt+) keybinding to the zoom actions. There must be some inconsistency on how those labels are made. 2015-07-01 2:37 GMT+02:00 Simon Richter simon.rich...@hogyros.de: Hi, I've just tried to get context sensitive help using the F1 key, and found that instead it zoomed in. The menu claims that the hotkey for zooming in is Alt-F1, while the hotkey list accessible with the '?' key lists F1 without qualifiers. On Mac, Ctrl-'+' is used instead, which is fairly common in PC software as well these days (IE and Firefox, for example). Would it make sense to offer Ctrl-'+' and Ctrl-'-' on all platforms? Would it make sense to reserve F1 for context help? Simon ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Zoom vs Help
On top of that, the hotkeys list is mostly wrong on OS X in that it shows Ctrl- as the modifier key when in fact it is Cmd- on OS X. Garth On Jun 30, 2015, at 10:43 PM, Nick Østergaard oe.n...@gmail.com wrote: On a side note: Please note that the right click context menu shows the correct (without alt+) keybinding to the zoom actions. There must be some inconsistency on how those labels are made. 2015-07-01 2:37 GMT+02:00 Simon Richter simon.rich...@hogyros.de: Hi, I've just tried to get context sensitive help using the F1 key, and found that instead it zoomed in. The menu claims that the hotkey for zooming in is Alt-F1, while the hotkey list accessible with the '?' key lists F1 without qualifiers. On Mac, Ctrl-'+' is used instead, which is fairly common in PC software as well these days (IE and Firefox, for example). Would it make sense to offer Ctrl-'+' and Ctrl-'-' on all platforms? Would it make sense to reserve F1 for context help? Simon ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
