RE: OSX long file names

Thanks, Charles and Joe. Makes a lot more sense now. ___ Unsubscribe or switch delivery mode: Search the archives of this list here:

Re: OSX long file names

> FolderItem.GetSaveInfo returns a REALbasic string with nil encoding. > Thus it is not "text". What EncodeBase64 does is to take binary data > and encode it as an ASCII string. Got it - thanks! - John ___ Unsubscribe or switch delivery mode:

Re: OSX long file names

On Jun 8, 2006, at 11:15 AM, John McKernon wrote: Ah. For this you should use FolderItem.GetSaveInfo. To store the data in a text file, you should encode the data using Base64, which returns "text". Would you recommend doing this when storing all strings in a text file? As I understand

Re: OSX long file names

> Ah. For this you should use FolderItem.GetSaveInfo. To store the > data in a text file, you should encode the data using Base64, which > returns "text". Would you recommend doing this when storing all strings in a text file? As I understand it, RB automatically uses UTF8 encoding when writing

RE: OSX long file names

On Jun 08, 2006, at 04:38 UTC, RBNUBE wrote: > Can you give me a specific example of where I might run into problems if I > don't use Base 64? Sure: suppose the binary data happens to contain a byte that's the same byte as an end-of-line sequence. TextInputStream.ReadLine will then stop reading

Re: OSX long file names

On Jun 8, 2006, at 12:39 AM, RBNUBE wrote: Would you remind me what exactly are you trying to accomplish? Storing a reference to a folder in a text file without using an absolute path. Ah. For this you should use FolderItem.GetSaveInfo. To store the data in a text file, you should en

RE: OSX long file names

>Would you remind me what exactly are you trying to accomplish? Storing a reference to a folder in a text file without using an absolute path. ___ Unsubscribe or switch delivery mode: Search the archiv

RE: OSX long file names

Thanks, Joe. I took your advice, and it seems to work fine. Can you give me a specific example of where I might run into problems if I don't use Base 64? ___ Unsubscribe or switch delivery mode: Sea

RE: OSX long file names

On Jun 07, 2006, at 02:50 UTC, RBNUBE wrote: > I've been looking into this, and I haven't seen anyone mention base 64 > encoding. No? That's the standard solution for storing a file reference in a text file or database -- EncodeBase64 the GetSaveInfo, and in reverse, DecodeBase64 and pass it t

Re: OSX long file names

Would you remind me what exactly are you trying to accomplish? Charles Yeomans On Jun 6, 2006, at 10:50 PM, RBNUBE wrote: I've been looking into this, and I haven't seen anyone mention base 64 encoding. I made a test project that seems to be working fine. This was created from bits and pi

RE: OSX long file names

I've been looking into this, and I haven't seen anyone mention base 64 encoding. I made a test project that seems to be working fine. This was created from bits and pieces of info found on the internet. PushButton1 creates a text file, writes a path to it. PushButton2 opens the text file, reads

Re: OSX long file names

Mario Buchichio <[EMAIL PROTECTED]> wrote: > That's true, but to store the GetSaveInfo returned value in a text file > one need to maybe encoded in Base64, am I right? yes. Gruß Christian -- Around eleven thousand functions in one REALbasic plug-in. The Monkeybread Software Realbasic Plugin v

Re: OSX long file names

That's true, but to store the GetSaveInfo returned value in a text file one need to maybe encoded in Base64, am I right? I guess because I think the GetSaveInfo string return non ascii values, if I remember correctly. I have learned that too, but how do you store references to files in a docu

Re: OSX long file names

On Jun 04, 2006, at 8:01 PM, Mario Buchichio wrote: I have learned that too, but how do you store references to files in a document or text file? look at the GetSaveInfo method for a folder item you can save that and use it to then get access to the same item later by creating a folder ite

RE: OSX long file names

That's a good question. I'm writing something that deals with 'watched folders,' including folders on a network, and I don't see a good way to deal with this situation. ___ Unsubscribe or switch delivery mode:

Re: OSX long file names

I have learned that too, but how do you store references to files in a document or text file? Regards! Sven E Olsson escribió: On May 28, 2006, at 8:58 PM, RBNUBE wrote: I have a feeling that it's the use of AbsolutePaths. One of these days I will learn not to use them even on Windows ap

RE: OSX long file names

AbsolutePaths was the problemI think I've learned my lesson :) ___ Unsubscribe or switch delivery mode: Search the archives of this list here:

Re: OSX long file names

On May 28, 2006, at 8:58 PM, RBNUBE wrote: I have a feeling that it's the use of AbsolutePaths. One of these days I will learn not to use them even on Windows applications that I think will never be used on Mac... Creating folderitems from absolute path is the same as 7 year in prison.

RE: OSX long file names

I have a feeling that it's the use of AbsolutePaths. One of these days I will learn not to use them even on Windows applications that I think will never be used on Mac... ___ Unsubscribe or switch delivery mode:

OSX long file names

It seems that if the file name is too long, I'm having problems renaming files on OSX. I have a ListBox where filenames are listed. A button is pressed and the files are renamed based on information in an EditField. At first, the names in the ListBox appear to correct. Once I try to rename them