Error getting tags :
error 404Error getting tags :
error 404 revMacFromUnixPath | revDocs | RunRev
Welcome Guest (Log in)
Product Edition
Version
revMacFromUnixPath
Basics
Expander triangle
Type
Function
Syntax
revMacFromUnixPath(unixPathname[,convertOSX])
Introduced
1.0
Changed
2.1.1
Environment
Desktop, Web and Server
Platform Support
MacOS,Mac OS X,Windows,Linux
Security
None required
Summary
Converts a Unix-style pathname to a Mac OS-style pathname.
Examples

revMacFromUnixPath("/usr/bin/stuff") -- returns "usr:bin:stuff"
revMacFromUnixPath(it)
revMacFromUnixPath(

Additional Comments
Expander triangle

Use the revMacFromUnixPath function to convert a Revolution-style file path to the Mac OS file path format (for example, if you need to pass a pathname to an external).

Parameters:

The unixPathname is a file or folder pathname in the standard format used by Revolution for file paths.

The convertOSX is true or false. If you don't specify the convertOSX, if OS X is running, Revolution assumes you want to convert an OS X-style path to a Mac OS-style path; otherwise, it assumes you don't want to convert between the OS X style and Mac OS style.

Value:

The revMacFromUnixPath function returns a string with the file path in the format expected by the Mac OS.

Comments:

The revMacFromUnixPath function converts slashes (/) to colons (:), the folder-level delimiter for Mac OS pathnames. It also deletes leading slashes, so that pathnames are rooted in the volume name (the standard for Mac OS pathnames). It also adjusts relative pathnames.

On Mac OS systems, absolute paths always begin with the name of the disk that the file or folder is on. On OS X systems, the startup disk's name does not appear in absolute file paths. Instead, if a file or folder is on the startup disk, the first part of the file path is the top-level folder that the file is in. If a file or folder is on a disk other than the startup disk, its absolute path starts with "Volumes", followed by the disk name.

The OS X path convention is used by Revolution, but the old Mac OS-style path convention is required by certain applications (such as AppleScript), even on OS X systems. If the convertOSX is true (or if you don't specify the convertOSX and the application is running under OS X), the revMacFromUnixPath function automatically converts absolute paths from the OS X standard to the Mac OS standard, adding the startup disk's name to paths that are on the startup disk, and stripping the "Volumes" element from paths that are not on the startup disk. If the convertOSX is false, the revMacFromUnixPath function does not make these changes to absolute paths.

Revolution always uses the Unix pathname standard for cross-platform compatibility, and automatically converts pathnames to the correct standard for the current platform when executing commands. You need to convert the pathname only if you are passing it to another program or external. If you are using only Revolution commands and functions, you do not need to convert the pathname, since Revolution does it for you.

Note: When included in a standalone application, the Common library is implemented as a hidden group and made available when the group receives its first openBackground message. During the first part of the application's startup process, before this message is sent, the revMacFromUnixPathfunction is not yet available. This may affect attempts to use this function in startup, preOpenStack, openStack, or preOpenCardhandlers in the main stack. Once the application has finished starting up, the library is available and the revMacFromUnixPathfunction can be used in any handler.

Changes to Revolution:

The convertOSX parameter was introduced in version 2.1.1. In previous versions, the revMacFromUnixPath function did not attempt to convert between the Mac OS and OS X conventions described above.

User Comments
Expander triangle