Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


We have a group of LibreOffice Bugs in the OS X builds related to keyboard
accelerators (<cmd>-A, <cmd>-C, <cmd>-V):

fdo#49853 <https://bugs.freedesktop.org/show_bug.cgi?id=49853>  
fdo#55914 <https://bugs.freedesktop.org/show_bug.cgi?id=55914>  
fdo#60790 <https://bugs.freedesktop.org/show_bug.cgi?id=60790>  
fdo#62054 <https://bugs.freedesktop.org/show_bug.cgi?id=62054>  

Spent a little time on StackExchange and found that non-association of the
keyboard accelerators is not that uncommon in NSMenu & NSView Objective C
Cocoa programming for OS X. And that the resolution is to associate the
accelerators to the corresponding menu of the component, or to the main
menu--which ever is the First Responder for the window or pop-up with focus. 

Some time in OpenGrok suggests problem lies in the

http://opengrok.libreoffice.org/xref/core/vcl/aqua/source/res/MainMenu.nib/
http://opengrok.libreoffice.org/xref/core/vcl/inc/aqua/salnsmenu.h
http://opengrok.libreoffice.org/xref/core/vcl/aqua/source/window/salmenu.cxx
http://opengrok.libreoffice.org/xref/core/vcl/aqua/source/window/salnsmenu.mm

source.  But I can find no hint of key bindings for the accelerators. Did it
simply get overlooked?





--
View this message in context: 
http://nabble.documentfoundation.org/Objective-C-Cocoa-NSMenu-FirstResponder-key-bindings-tp4047224.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.