Managing Long IDs?

[Scott Rossi]

Thanks Mark.  I was hoping there was some encoding thing I could do to
avoid having to translate paths back and forth, but of course that method
can work, and I suppose you'd have to decode an encoded string anyway.

A folder with commas in the name isn't totally implausible.  In this case,
they were using a date as the folder name to reference the contents.  You
and I would never do it, but they (understandably) saw a date as a
reasonable label.

Then there's the hell of slashes.  It seems you have to test for a colon
on OS X.

(Hmm.  That last sentence could be read in a number of ways.)

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 7/15/13 4:08 PM, "Mark Wieder" <mwieder at ahsoftware.net> wrote:

>Scott-
>
>Monday, July 15, 2013, 3:12:00 PM, you wrote:
>
>> I recently worked with a client to trace some non-functioning behavior
>>in
>> a stack to the use of commas in a folder name where the user placed the
>> application and support files. I always use long ids for object
>> references, so of course my scripts tripped up where the default
>> itemDelimiter (comma) was used.
>
>Commas in a folder name? WTFclients?
>
>Long ids have the file path enclosed in quotes, so ideally the comma
>there shouldn't be an issue unless you're trying to pick the path
>apart. I've had similar situations with commas in property names (I'm
>looking at you, IDE) and dealt with it by
>
>replace comma with "_MAGIC_COMMA_" in tString
>
>and then done the reverse replacement on the way out.
>
>-- 
>-Mark Wieder
> mwieder at ahsoftware.net
>
>
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode
>