lingo-l fileIO brain teaser
Just wondering if someone can add a new perspective to a problem. I am developing for a win system and using fileio. Currently fileIO has a problem with paths over 126 chars so I use BuddyAPI's baShortfilename to truncate the path. All good so far, but now the problem arises. The baShortFileName only returns a truncated name from a file that already exists and I'm currently using the create method of the xtra. Therefore I can't create the file because I can't trucate the path and I can't truncate the path because I can't create the file! (oooh my head hurts) Any other (inbuilt/free) Xtras that create files or truncate filenames available? Any way of truncating the filename using lingo so that Windows can read it? Thanks to all Brad [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l fileIO brain teaser
The baShortFileName only returns a truncated name from a file that already exists I did not know that. I thought it would create a short file path even if the actual file did not exist. I must admit though that I have only used the function on file paths that did exist. Therefore I can't create the file because I can't trucate the path and I can't truncate the path because I can't create the file! (oooh my head hurts) I could be wrong about this (it's been a while since I've used fileIO) but I thought fileIO only had a problem with long file paths in the openFile() function. With the createFile() function you should be able to use a normal file path without having to resort to the baShortfilename() function. I'm at home right now (no PC here, only a Mac) so I can't test this theory. If I'm wrong then you can blame my memory on the aging process. I am off to bed now (another reason to blame my short memory... lack of sleep). I hope this helps. ck [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l fileIO brain teaser
The DOS command path (including file names) is limited to 255 chars, not sure about internal limits on FileIO. Short names are generated by the operating system; there is no way to know ahead of time what it will be (although you could write an algorithm to guess, based on existing files, since it does follow a pattern). What you could do is use short names for all the folders/directories leading up to the file, and then just a long name for the file itself. If the file itself has to be over 128 chars, then I would question WHY you need a file with a name that long. But if you short-name the folders that preceed it, you can get away with a lot less space for the same name, as in: C:\Progra~1\Micros~1\my long filename here - Tab At 03:41 AM 11/30/02, Brad Hile wrote: Just wondering if someone can add a new perspective to a problem. I am developing for a win system and using fileio. Currently fileIO has a problem with paths over 126 chars so I use BuddyAPI's baShortfilename to truncate the path. All good so far, but now the problem arises. The baShortFileName only returns a truncated name from a file that already exists and I'm currently using the create method of the xtra. Therefore I can't create the file because I can't trucate the path and I can't truncate the path because I can't create the file! (oooh my head hurts) Any other (inbuilt/free) Xtras that create files or truncate filenames available? Any way of truncating the filename using lingo so that Windows can read it? Thanks to all Brad [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l fileIO brain teaser
At 16:41 30.11.2002 +0800, Brad Hile wrote: The baShortFileName only returns a truncated name from a file that already exists and I'm currently using the create method of the xtra. Therefore I can't create the file because I can't trucate the path and I can't truncate the path because I can't create the file! (oooh my head hurts) hm, it smells just like a workaround, but - what about having an (empty) dummy file which you then copy, rename, baShortFilename(), and open? Daniel [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l upgrade price
All, You know, I just realized there's no osx/mac version of flash comm. SO, being that the price is with a flash comm server, and that's only win, is it fair that both platforms be the same price? 1. Your upgrade price covers the cost of Director, extra apps are generally thrown in and MACR eats the cost. 2. Mac OSX users will get a Windows copy of Flash Communication Server too. Cheers, Tom [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
Re: lingo-l upgrade price
Well, they could price fairly by platform...in which case the PC version which didn't change much would be about $25 a copy, and the Mac version which had to be overhauled in india, could cost $3000 or so a copy... I wonder what the sales volume per platform is today. Charted back in time, too. roymeo At 06:14 PM 11/30/2002 -0600, you wrote: You know, I just realized there's no osx/mac version of flash comm. SO, being that the price is with a flash comm server, and that's only win, is it fair that both platforms be the same price? [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!] [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
RE: lingo-l upgrade price
On Sat, 30 Nov 2002, Thomas Higgins wrote: 1. Your upgrade price covers the cost of Director, extra apps are generally thrown in and MACR eats the cost. 2. Mac OSX users will get a Windows copy of Flash Communication Server too. Hey Tom - et al Don't misunderstand; I _certainly_ think director is worth it - and am going to spew forth the upgrade price posthaste; but I guess what i'm trying to say is that if one is primarily an osx-native developer, the flashcomm server for win really does one no good. Plus, since I've got to buy the pc version, I'll have 2 versions of flashcomm; again running an osx server rather than win server, I wouldn't really use them (personally, although to be truthfull I'll probably set up a win dev server to play with). Now, for those that do have a win server, is there a way to buy both platforms and get a say, 2 megabit or 20 max connection server rather than 2 servers? Any chance at any time of developing a unix flash comm server? [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
