Product Logo

CNS Menu

Dynamic Menus


Runtime Solutions

Using a Runtime Solution and want to use the plug-in? No problem, CNS Menu will work in Runtime Solutions!

Installation

Installing a plug-in in a Runtime Solution is just as easy as installing it in FileMaker Pro. If the Runtime Solution is open, then close it. Next, locate the folder on your hard drive that contains your Runtime Solution. Next to the Runtime application, you should see a folder named Extensions. If this folder does not exist, create it. Copy the plug-in file into this folder to install it into your Runtime Solution.

Figure 1 Runtime Solution Folder

Configuration

If you want to use the Configuration Dialog in a Runtime Solution, it works the same as when in FileMaker Pro. See the Configuration section for more information. Note, accessing the Configuration Dialog is different when working in Kiosk Mode. See the Kiosk Mode section below for more information.

Registration

Registering the plug-in works just the same as when using it in FileMaker Pro. It can either be done in the Configuration Dialog or using the CNSMenu_Register function in a script. See the Registration section for more information. Note, registering via the Configuration Dialog is different when working in Kiosk Mode. See the Kiosk Mode section below for more information.

Using the plug-in

The plug-in works exactly the same as when using it in FileMaker Pro. Any script that works in FileMaker Pro will work just the same in your Runtime Solution.

Kiosk Mode

If you are running your Runtime Solution in Kiosk Mode, then registering and configuring the plug-in is slightly different if you want to use the Configuration Dialog. In this mode, FileMaker does not display any of the menus, so there is no way to access the list of installed plug-ins nor the plug-in’s Configuration Dialog. To open the plug-in’s configuration dialog, use the following function call in a Set Field or Set Variable script step.

CNSMenu_Configure

Known Issue

On some Windows computers (this does not affect Macs), after installing the plug-in, the Runtime Solution will open one time, but if you close it and attempt to re-open the Runtime Solution, it will not work unless the computer is restarted. The Runtime Solution process will show up in the Windows Task Manager, but will never actually open. We currently do not have a fix for this, but there is a simple work around method to allow the Runtime Solution to open properly.

  1. Open the Extensions folder inside your Runtime Solution folder.
  2. Check if you are using plug-ins from any other vendor. If so, skip to step 6.
  3. Open the folder for the normal FileMaker Pro installation. Note, this may need to be done on a different computer if the normal FileMaker Pro program is not installed. It is normally located at C:\Program Files\FileMaker\FileMaker Pro</li>
  4. Open the Extensions folder found inside the FileMaker Pro folder.
  5. Find the file named “FMSAUC.fmx”, and copy it into the Runtime Solution Extensions folder.
  6. Inside the Runtime Solution Extensions folder, find the “CNS_Menu_WIN.fmx” file and rename it to “zCNS_Menu_WIN.fmx”. In other words, place the letter “z” at the beginning of the plug-in filename.
Figure 2 Runtime Extensions Folder

This work around forces the Runtime Solution to load some other plug-in prior to loading CNS Menu, because it loads the plug-ins alphabetically. Adding the “z” is not magic, but simply changes the order in which the plug-ins are loaded, and allows it to work correctly. Adding the “z” to the plug-in in no way affects the plug-in or your scripts, and it will continue to function normally. We are sorry for the inconvenience, and hope to have this issue resolved in a future version.