To clarify, the screenshot below shows how our custom menu item is setup:
Your custom menu method is very clever.
Three work arounds come to mind:
- Put this auto-enter calculation on the field: TextFormatRemove ( Self ) and Clear the "Do not replace existing value..." check box.
- Instead of a custom dialog (don't really care for their limitations anyway), use new window to open a modal dialog for your data entry and pasting. This will now work with your custom menu.
- And what I now use in place of custom dialogs and New Window nearly always: Use a Popover. This will also work with your custom menu.
Thanks, Phil! I like your #2 and #3 options (particularly #3, to reduce window clutter & window management). #1 is a good trick too, but it would require putting that auto-enter calculation on every single field that could ever possibly be pasted into from an external source.
But the original report is not absolutely thorough. I think the situation is worse.
Using myself the same method as Scotty, i also have trouble when using developer's dialog, since the opening of a "manage" window or the data visualizer does not switch automatically to standard menu. Known issue.
And strangely, if you take the data visualizer, you will not be able to copy past even text, when the "Paste without style" command is activated. It is also true with Database, Custom function etc... for obvious reasons, since you can paste more than just text but also fields, tables, scripts etc...
Actually, you would only use 1. for those few fields where you want to use them with input boxes in a custom dialog. Your established method would be used with all of the other fields.
Thanks, Fred... I totally forgot about that! Huge problem! Pasting doesn't work in any of the developer areas of the program, unless you have the standard paste menu installed!
Phil, I'm not sure if the custom dialog box will allow people to paste formatted text into the dialog box... I will have to test. I'm assuming that if it does, then the auto-enter calc would trigger after the commit. Although that still doesn't solve the problem of wanting users to only paste plain text throughout the entire system. Would still need a custom menu to elegantly solve that problem for all fields throughout the entire system.... Which would bring us back to the original problem again. It is a circular problem!!
There's no circle.
Leave your custom menu in place as the "default setting".
When your script opens the custom menu, install the standard FileMaker menu set so that they can paste.
The auto-enter calc will then strip out any formatting on your input fields.
After the dialog is dismissed install the original menu set.
Right, but my whole point is that I don't want to install the standard FileMaker menu set and then re-install my custom menu set again.
You do know that I am referring to the script doing the custom menu installs? And only for the time that the custom dialog is waiting for a mouse click to close it?
And such is the nature of Work Arounds. They typically require you to do extra work, but hopefully they then enable you to get the job done so that you are not stalled waiting for FileMaker to fix the problem.
But the worries i was talking about concerning the developer's windows are more painful than a usual workaround, since you have to domestic your brain to do the menu change manually; you cannot trip a script when Data Visualizer is opening. And setting the default value as standard menu set dos not solve this specific issue, at least on OS X.
Well said ! And for who use Mac as well as PC it would be a bit hard to memorize, since it is a Mac only (unaknowledged) issue.
Yep, still waiting for a TS person to acknowledge before I add a report to the KBL database.
Thank you for your post.
Using the [Standard FileMaker Menus], with a Show Custom Dialog active with an Input field, only "Paste" is highlighted in the Edit menu. "Paste Text Only" is grayed out. Therefore, command-V works, while command-shift-V does not.
When I set up a custom menu (TEST) with your same options, the "Paste Without Style" also fails, while the "Paste" option (command-shift-V) works. Interestingly, the "Paste Without Style" option is not grayed out, so I'm not sure if the issue is with the command itself, or if the highlighting is incorrect. I have sent this issue to our Development and Testing departments to let them determine the issue. When I receive any feedback, I will let you know.