Ah ok so just checked the docs on the array encode version added in LC 7 and
found:
```
If present, and >= "7.0" then the array is encoded in such a way as to preserve
unicode in keys and values, as well as NUL chars in keys and values
```
So try `arrayEncode(array, “7.0")`
> On 19 Feb 2025, at
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.
C
Okay I don’t think I am having an issue with arrayEncode. I think I am having
an issue where arrayEncoding with MacOS is failing to arrayDecode in Windows
and vis versa.
Bob S
> On Feb 18, 2025, at 1:28 PM, Bob Sneidar via use-livecode
> wrote:
>
> Hi all.
>
> I think I have uncovered an
Ahah!
Okay I can do that, but I also determined that if I base64encode the encrypted
data before putting it into the [n] [“data”] key then reverse on the other end,
it works as well. Same idea, different technique.
Bob S
> On Feb 18, 2025, at 3:29 PM, Monte Goulding via use-livecode
> wro
Thanks Monte.
Here is what I am doing:
I have a numbered array. Element 0 has a key called operation which simply has
a string with one of several possible values.
Then I have elements 1 to n with a number of different elements, most are
simple strings, but one key is the binary file data o
> On 19 Feb 2025, at 9:09 AM, Bob Sneidar via use-livecode
> wrote:
>
> Okay I don’t think I am having an issue with arrayEncode. I think I am having
> an issue where arrayEncoding with MacOS is failing to arrayDecode in Windows
> and vis versa.
The result of arrayEncode is a binary string
> On 19 Feb 2025, at 9:39 AM, Bob Sneidar via use-livecode
> wrote:
>
> but one key is the binary file data of a file that has been encrypted using
> LC’s built in library.
Are you using this as the key or element value? I think keys are always treated
as text. It has been quite one time
The structure looks like the following:
Sly File Agent API
Structure of payload sent
[0]
[profile]
[n]
[data]
[datemodified]
[extpath]
[filecategory]
[fileid]
[filename]
[filepath]
[operation
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.
