"calvaryftl" wrote:
Well, all I know is that my server is not case sensitive, but the parseJson function specs specify:
Any roAssociativeArray objects in the returned objects will be case sensitive.
It seems to me that somehow, the case sensitivity must be in the code.
But it's not worth debating. 🙂 Just a possible gotcha to look out for.
That statement is referring to the object's keys, not the values (values
always retain case). So, if your JSON object had two keys, one named "test" and a second named "TEST", they'd be treated as two separate properties, unlike standard BrightScript which would treat them as the same key.
My guess would be that you either had a minor typo or an extra character (maybe whitespace) in the URL that you corrected inadvertently when you re-cased it. Important part is that you got it working, so you're right, not worth debating.
My Channels: http://roku.permanence.com - Twitter: @TheEndlessDev
Instant Watch Browser (NetflixIWB), Aquarium Screensaver (AQUARIUM), Clever Clocks Screensaver (CLEVERCLOCKS), iTunes Podcasts (ITPC), My Channels (MYCHANNELS)