什么决定何时禁用 FileMaker 自定义菜单?

发布于 2024-11-17 05:52:27 字数 425 浏览 7 评论 0原文

我构建的系统大量使用了 FileMaker 中的自定义菜单。当我以完全访问权限登录并安装带有这些自定义菜单的菜单集时,它们看起来很好。但是,当非完全访问用户登录时,它们将被禁用。这包括大多数自定义菜单,但不是全部。

例如,我保留了“文件>更改密码”选项,并且我登录的用户有权更改其密码,但“更改密码”菜单项被禁用。

其他禁用的菜单包括我放置在“视图”菜单中的菜单,用于导航到系统的不同部分,例如“主页”、“人员”、“公司”等。这些项目的功能在按钮中重复,并且它们可以工作,但菜单是禁用。这些按钮使用完全相同的参数调用完全相同的脚本。

或者,保留并启用“文件>关闭”命令。因此,“关闭”和“更改密码”均基于现有命令,但其中一个已启用,另一个未启用。我似乎找不到启用的菜单与禁用的菜单有任何共同点。

那么,什么情况下自定义菜单项会被禁用呢?

谢谢, 查克

I have a system that I've built that makes heavy use of custom menus in FileMaker. When I log in as full access, and install the menu set with these custom menus, they appear fine. However, when a non-full access user logs in, they're disabled. This includes most of the custom menus, but not all.

For example, I have left the File>Change Password option in and the user I'm logging in as has the permission to change their password, but the Change Password menu item is disabled.

Other disabled menus include those I've placed in the View menu to navigate to different sections of the system, such as Home, People, Companies, etc. The functionality of these items is duplicated in buttons, and they work, but the menu is disabled. The buttons are calling the exact same script with the exact same parameter.

Alternatively, the File>Close command is left in and is enabled. So both Close and Change Password are based on existing commands but one's enabled and the other isn't. I can't seem to find anything in common with the menus that are enabled vs. those that are disabled.

So, under what conditions will a custom menu item be disabled?

Thanks,
Chuck

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

寂寞美少年 2024-11-24 05:52:27

在线文档有关菜单何时变暗的说明如下:

如果用户没有执行菜单命令的权限,标准 FileMaker 菜单项会呈灰色显示。如果将脚本附加到菜单项,菜单不会变暗。

话虽这么说,我想知道您是否没有遇到变暗的情况,因为菜单基于他们无权访问的现有命令。我会尝试以下操作:

  1. 暂时关闭自定义菜单,然后以无权访问“更改密码”选项的用户身份登录。使用默认菜单集时它仍然变暗吗?如果是这样,听起来您遇到了权限问题,应该进一步探讨该问题。
  2. 在权限“编辑权限集”窗口中查看“可用菜单命令”选项并了解其设置方式。如果未设置为“全部”,请尝试将其更改为“全部”
  3. 对于“视图”菜单,请查看自定义菜单项并查看是否选择了“基于现有命令:”。如果菜单项正在执行脚本,请尝试取消选中“基于现有命令:”并查看是否会更改调光行为。
  4. 确保用户有权运行菜单调用的任何脚本。

祝你好运!

The online documentation says the following about when menus are dimmed:

Standard FileMaker menu items are dimmed if users don’t have privileges to perform the menu command. Menus are not dimmed if you attach a script to the menu item.

That being said, I wonder if you aren't encountering dimming because of the menus being based on an existing command which they don't have access to. I would try the following:

  1. Turn off your custom menu for a moment and log in as the user who doesn't have access to the Change Password option. Is it still dimmed using the default menu set? If so, it sounds like you have a permissions issue and should explore that further.
  2. In the permissions 'Edit Permission Set' window take a look at the 'Available Menu Commands' option and see how that is set up. If it's not set at 'All' try changing it to 'All'
  3. For the View menu, look at the custom menu items and see if you have 'Based on existing command:' selected. If the menu item is performing a script, try unchecking 'Based on existing command:' and see if that changes the dimming behavior.
  4. Make certain that the user has permission to run any script which the menu calls.

Good luck!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文