<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none"></style> </head> <body dir="ltr"> <div id="OWAFontStyleDivID" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;"> <p></p> <div>A couple of notes on the previous emails,</div> <div><br> </div> <div>Fabrice, so long as your app ensures that no third-party code can programmatically grab a shortcut without user agreement, it would make sense to let it have a privilege.</div> <div><br> </div> <div>Quite obviously a compo should have the last word and be able to refuse a request to grab a certain shortcut. If this happens, compo developers please do provide the requesting app a displayable/translatable explanation that your end-users would understand ;)</div> <div><br> </div> <div>I don't quite like the idea of a permission prompt from the compo for setting up keyboard shortcuts. In the vast majority of cases the user is already using a specific GUI for that and possibly setting up more than one shortcut (e.g. shortcuts to newly installed media app), so it'd be awkward for them to receive a permission prompt. I think privileges work much better here (or User-Driven Access Control with a button that when clicked displays a compositor-owned dialog inviting the user to select a global shortcut).</div> <div><br> </div> <div>--<br> </div> <div>Steve<br> </div> <p><br> </p> </div> </body> </html>