a few days ago I added a feature for a client to disable contextual menu for Mac and Windows.
Yesterday I had an idea and now I'd like to ask whether the fine developers here could tell me whether this is a good idea:
When FileMaker shows a menu, the MBS Plugin could put itself between FileMaker and the OS and catch the notification about the menu actions. So when you choose a menu command, our plugin would get to do something first before the menu action is sent to FileMaker app itself.
We could filter menu commands by ID, e.g. you could define that menu command 50281 (exports to excel) is blocked in addition to the FileMaker security checks.
Or we run even an evaluate for a menu action and see if it returns 1 before blocking, so you could decide on some global variables.
What do you think?
As I didn't try yet to build this, it is not known how much effort it would need and whether it'll work. As usual the feature would only be installed if you call a function.
What comes to my mind is catching in adverted ESC action on MacBoks with Touch Bar. Under Windows, certain modifier keys are ignored by FM and no action is triggered. Not sure if this is within the scope of your question.
We already have a preferences on MacOS to replace ESC with option-ESC for the Touch Bar MacBooks when using internal keyboard. This avoids the unintentional dialog closures.
as we know, with macOS, it's still possible with right mouse click on the upper window frame, to configure/activate, toolbar and so give access to task such as create/delete record.
As with your "Ruberband-Function", it would be nice to securely shut this off.
how is this different than what can be achieved with custom menus?
would the same interception work if the user summons the menu item via a keyboard shortcut (a standard one, one defined via MacOS, one defined via custom menus)?
could it also be done for menu items created with custom menus?
would a custom menu item "based on existing command" also inherit this MBS customization?
How I see this at this time (it could evolve)
I fail to see what this achieves that cannot already be achieved with custom menus (aside from the next point)
FileMaker won't let us customize some menu items with custom menus, so it could be used for that, but it sounds like a lot of effort for a use case that I do not come across often.
How could I miss this!
Just fixed a longtime annoyance.
If you find, by any chance, my dedicated FM Bug Report I sent in a couple of Years ago, feel free to add this work around:
