The syntax in the new API looks like this: Dial_Dialog(switches The plug-in functions have a different syntax compared to the FileMaker 6 plug-in.įor example the Dial_Dialog function has this syntax in the classic API: External("TrDl-DialogEx", "switches|text|button1|button2|button3|button4" ) Below are some considerations when converting to Troi Dialog Plug-in 4. Troi Dialog Plug-in 4 was created specifically for FileMaker Pro 7. Troi Dialog Plug-in 4.0 (Native FileMaker 7 API) We have not tested earlier versions, but we expect versions 3.5.1 or older of the plug-in to work with FileMaker 7, however this latest version has some bug fixes too, so it is strongly recommend that you use the latest version. We have tested version 3.5.2 and version 3.5.3 with FileMaker 7 and this works similar as version 3.6. The Dialog Plug-in 3.6 is using the classic API, so only characters in the ASCII range will work.
In general our plug-ins should be compatible as long as the text used is lower ASCII text. ALL plug-ins written for the 'classic' FileMaker 6 architecture do not receive characters that are outside this ASCII range, these characters are replaced with spaces. FileMaker Pro 6 only used ASCII encoding. General Issue for all Classic plug-ins with higher ASCII'sįileMaker Pro 7 has a new internal architecture, which is using Unicode for the text fields. See also the fp7 example files of Troi Dialog 3.6, which have this modification applied. This will pause FileMaker long enough to get the icon on the clipboard.
If # This step below is needed on Windows and FileMaker 7, to make sure the icon is properly set. If for example you have this script in a FileMaker Pro 7 file: Copy To prevent this you must change the scripts with the TrDl-IconControl function. This will result in a $$-4239 error (kErrClipboardNotOpen) from the TrDl-IconControl function of the plug-in. The current version of FileMaker 7 seems to have a bit of delay in updating a the clipboard, after you have used the Copy script step. This will cause the progress bar and text to be directly visible.
UPDATE To improve this: Add an extra Pause/Resume step of 0 seconds after the 'show' step. After a short delay it will show the correct contents. You will first see the dialog window, without any text and progress bar drawn in. This results in a delay in showing the contents of the progress bar. Delay in visibility of the TrDl-ProgressBar functionįileMaker Pro 7 has a subtle change in how it handles plug-ins.
We have found no other issues with FileMaker 7 than the ones below. Troi Dialog Plug-in 3.6 in general does work with FileMaker Pro 7, without modification. Troi Dialog Plug-in 3.6 is compatible with FileMaker 7 Please only use Troi Dialog Plug-in 4.0 for FileMaker Pro 7 and only use Troi Dialog Plug-in 4.5 for FileMaker Pro 8 and 8.5. TIP Although you can use both Troi Dialog Plug-in 3.6 and Troi Dialog Plug-in 4.0 together when running FileMaker 7, this is not recommended. NOTE The function API is the same for FileMaker Pro 7 through FileMaker Pro 15. (This page was last updated July 18th, 2006.) Below you find a discussionof both plug-ins.īelow we will discuss Troi Dialog Plug-in 4.0, but this also should apply to future versions with a higher number, for example version 6.0. We have two flavors of Dialog plug-ins: Troi DialogPlug-in 3.6 which uses the Classic API (function syntax) and TroiDialog Plug-in 4 (or higher) which uses theFileMaker 7 Native API introduced with FileMaker 7.
Overview | download | details | screenshots | comments | buy-it Troi Dialog Plug-in conversion from FMP6 Troi Dialog Plug-in adds powerful dialog functions to FileMaker Pro. Troi Dialog Plug-in 6.5.1 FileMaker Pro 12 through 15 compatible Conversion of Troi Dialog Plug-in from FileMaker 6