Jellybean wrote:Ok, it IS possible to do it "manually" by using the functions you described, but that's a bit like point people to the 2D Drawing lib when they want to create button. Sure, you could draw a button using pixels, but there are better ways.
Everyone can be wrong. It is NOT possible to do it by using the FileSystem lib.
CopyDirectory() returns a long, so clearly not the correct filepath.
CopyFile() returns a long, so clearly not the correct filepath.
CreateDirectory() returns a long, so clearly not the correct filepath.
DeleteDirectory() returns a long, so clearly not the correct filepath.
DeleteFile() returns a long, so clearly not the correct filepath.
DirectoryEntryAttributes() returns a long, so clearly not the correct filepath.
ExamineDirectory() returns a long, so clearly not the correct filepath.
NextDirectoryEntry() after ExamineDirectory() returns a long, so clearly not the correct filepath.
DirectoryEntryName() after NextDirectoryEntry() after ExamineDirectory() returns a string, but, as the description says, it returns the filename. Not including the path.
DirectoryEntrySize() returns a long, so clearly not the correct filepath.
FileSize() returns a long, so clearly not the correct filepath.
IsDirectory() returns a long, so clearly not the correct filepath.
IsFilename() returns a long, so clearly not the correct filepath.
RenameFile() returns a long, so clearly not the correct filepath.
UseDirectory() is an internal PB command and doesn't return anything at all.
None of the commands in the file library can be used for this, either.
So please, netmaestro, can you tell me how you would do this?