![]() 4.2.0 : Reverted back to the 4.0.5 and fixed the crash issue, and added executeUsingShell as an option. MacOS, Linux and iOS enable multiple calls to shell like version 4.0.5. 4.1.3 : Do not crash when attempting to execute an empty command. 4.0.6 : Switched to a different library, which broke a lot of things, and meant it could only run one command at a time. Keywords: Execute System Command Shell Version History: executeUsingShell : ( defaults to true ) whether to execute the command directly or in a shell timeout : A value, in milliseconds that the plugin should wait for a result before returning. command : the content of the command to run Setting this to false is gets the same compatibility as the 4.0.6 through 4.1.4 versions. Setting to false will require full paths, but can be more compatible. Plus it has access to the shell environment variables etc. TheexecuteUsingShell default is true, which means you can include multiple commands in a single command, like you would on unix. This is the same as if the parameter was left out. This is also equivalent to passing the parameter with only the command and no timeout parameter.Ī timeout value of 0 or and empty parameter "" will return to FileMaker immediately and will always return the error code 12000 - timeout exceeded.Īny other timeout value will wait a maximum of the time in milliseconds or when the command finishes, whichever is first. Using a timeout value of -1 will wait forever or until the command finishes. Close to the same as using Terminal on the Mac, or CMD.exe on Windows, but with lots of caveats as to the differences ( see Notes below ). Performs a command line script of the command parameter. ![]() ConvertFromFileMakerPath ( $filemakerPath PosixPath ) //Convert FileMaker to Mac/Linux Plugin PathĬonvertFromFileMakerPath ( $filemakerPath WinPath ) //Convert FileMaker to Windows Plugin PathĬonvertToFileMakerPath ( $pluginPath PosixPath ) //Convert Mac/Linux Plugin Path to file://Mac path.ĬonvertToFileMakerPath ( $pluginPath WinPath ) //Convert Windows Plugin Path to file://Windows path.BE_ExecuteSystemCommand BE_ExecuteSystemCommand ( command ) A "plugin" path is the same as the PosixPath for Mac or Linux, and the WinPath for windows operating systems. The best way to convert paths is to use the native FileMaker functions ConvertFromFileMakerPath and ConvertToFileMakerPath. Note the consistency of the type of slash used, vs the difference in \ vs / in Windows/Mac. Windows : file:///C:/Users/John%20Smith/Documents/test.xlsx FileMaker Path Examples Mac : file:///Volumes/Clients/contacts.txt You can then adjust this path to suit whatever location you need, or to get an example of the difference between selecting a file on the desktop and running the Get ( DesktopFolder ) function. This will return an example of the sort of path used by the function. To get an example of the sorts of paths that the plugin uses, use the BE_SelectFile function in the Data Viewer, and choose a file with a known path. Windows : C:\Users\John Smith\Documents\test.xlsx Plugin Paths Examples Mac : /Users/John Smith/Documents/test.xlsx" So if you're mixing and matching FileMaker paths and plugin paths, you will need to convert them between the types in order to use them in other places. These file: prefixes that you get from things like the Get ( FilePath ) function and others, are unique to FileMaker and don't work anywhere else other than FileMaker itself, including not in the BE plugin. On the Mac, they usually start with /Volumes or /Users and on windows will be something like C:\Folder\Path.įileMaker paths often start with file: or filemac: and these WILL NOT work in the plugin. The paths used by the plugin are Operating System paths. Please note :įileMaker paths and plugin paths are not the same thing. ![]() Lots of the BE plugin functions use paths in the parameters or in values they return. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |