Hi Bob I strongly suspect a mis-diagnosis here. If you have your paths in an array then do `put arrayDecode(arrayEncode(myArray)) into myArray` do you still see a problem? If you do please report a bug as there is a lot of code that relies on arrayEncode/decode round tripping with no issues.
Cheers Monte > On 19 Feb 2025, at 8:28 AM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hi all. > > I think I have uncovered an issue with encoding / decoding arrays where some > array elements are file paths. I’m thinking that the forweard slashes are > interfering with the decoding process. I think this because the arrayEncoded > data has the actual paths still intact in the data stream. > > I can work around this by base64encoding / decoding any elements with file > paths, but I want to make sure that the array encoding process does in fact > have issues with certain characters, and if it does what are those > characters? Is there a list of them? Can I delimit them? > > Bob S > > _______________________________________________ > 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
