Jump to content

Turning interface buttons off.


fmow

This topic is 3756 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Is there any way to disable a Go or Pro interface button or an iPad menu item, the native ones that is, permanently or under some circumstances. I know you cannot script them so i m looking for another way to avoid this scenario where with a new record i trigger a script which is not triggered in the standard process.

Link to comment
Share on other sites

Custom menus. In FileMaker Go, custom menus can't add new menu items or change the names of existing ones, but you can override the native action of an existing menu item with a script of your own.

Link to comment
Share on other sites

Custom menus. In FileMaker Go, custom menus can't add new menu items or change the names of existing ones, but you can override the native action of an existing menu item with a script of your own.

Oh, lovely, can you? Thanks for the heads up, again. That just leaves the ******* new record button in the status bar which can't be scripted. You can't believe how many times I myself have clicked new record (I of course work with the bar on) from the bar instead of my interface... But then again it's off by default in all my layouts. Having said that I dread the time where the bar goes on from a fluke and someone clicks new record.

Link to comment
Share on other sites

I believe the new record button works the same way, overriding the matching custom menu item changes the button behavior; but I haven't tried it in the most recent version of FileMaker, so I could be mistaken.

 

If that doesn't work, another approach might be to use the file security settings to disallow record creation except through a script you provide that runs as [Full Access].

Link to comment
Share on other sites

I believe the new record button works the same way, overriding the matching custom menu item changes the button behavior; but I haven't tried it in the most recent version of FileMaker, so I could be mistaken.

 

If that doesn't work, another approach might be to use the file security settings to disallow record creation except through a script you provide that runs as [Full Access].

I like how you think! :)

Link to comment
Share on other sites

This topic is 3756 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.