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 |