The IDs aren't really stored, mostly acted upon. If any are stored, it's only done for the current session. And yes, I use long IDs in return-delimited lists.
Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/15/13 3:52 PM, "Monte Goulding" <mo...@sweattechnologies.com> wrote: > >On 16/07/2013, at 8:12 AM, Scott Rossi <sc...@tactilemedia.com> wrote: > >> Does anybody have a simple means of dealing with this? urlEncode? >> Something else? The end result is going to be available to anyone, so >> it's not reasonable to issue a "Don't place this app in a folder that >> contains commas in the name!" warning to users. > >Unfortunately my pull request implementing rugged id was rejected. That >would have worked well for you. You can always implement a >ruggedIDfromLongID function in LiveCode. The other thing is the problem >seems to be more in how you are storing your long ids rather than the >actual long id. Do you have them as an item in a list? > >Cheers > >-- >Monte Goulding > >M E R Goulding - software development services >mergExt - There's an external for that! > > > > > >_______________________________________________ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
