#include <nn/save.h> FSStatus SAVEOpenDirOtherNormalApplication( FSClient *client, FSCmdBlock *block, u32 uniqueId, u8 accountSlotNo, const char *path, FSDirHandle *dirHandle, FSRetFlag errHandling ); FSStatus SAVEOpenDirOtherNormalApplicationAsync( FSClient *client, FSCmdBlock *block, u32 uniqueId, u8 accountSlotNo, const char *path, FSDirHandle *dirHandle, FSRetFlag errHandling, const FSAsyncParams *asyncParams );
|client||Pointer to the client buffer.|
|uniqueId||The unique ID of the target.|
|accountSlotNo||The user account slot number.|
|path||Directory path. The relative path for the save directory for the specified user account. The length must be less than
|dirHandle||Pointer to the handle of the directory stream associated with the directory to open.|
|errHandling||Automatic error handling flag. Only the indicated error is returned.|
|asyncParams||(Async API only) Notification parameters for an asynchronous call.|
||The command was canceled.|
||System has too many directory points to create more.|
||Target not found.
The specified user account does not exist on this Wii U console.
||Specified path is not a directory.|
||The caller does not have correct access permission.|
||(Only for manually mounted devices) Media is not present.|
||(Only for manually mounted devices) Media is in some inaccessible condition.|
||(Only for manually mounted devices) The data is corrupted beyond repair. The volume needs format.|
||Successfully issued the request.|
||The specified user account does not exist on this Wii U console.|
||The argument is invalid.|
Opens the application save subdirectory specified in uniqueId and path, and creates the directory stream associated with that directory. The specification of the variation is 0. The position of the directory stream is set to the head.
The generated directory handle is stored in dirHandle when the process is completed.
Both the sync and the async style API functions are provided. To use the async API functions, set the user callback and parameters in asyncParams. For more information,
If you plan to run an application that uses these functions in an environment with a USB drive connected, the USB drive must be connected when you start the application and create the save data. If you plan to run the application in an environment without a USB drive connected, the USB drive must be disconnected when you start the application and create the save data.
If you prepare save data using the Save Data Manager menu item in the System Config Tool, note that this function can only access save data that exists in NAND and USB storage,
not on the host PC. Also note that to access save data in NAND, the application that uses these functions needs to be launched using
caferun in an environment that is not connected to a
2014/10/22 Revised the return values.
2014/06/04 Added the specifications of the variation to description.
2013/05/23 Initial version.