I've ran into an issue where a sound file i wanted to loop wasn't and i've tracked it down to the fact that specifying looping = true inside the createSound definition is ignored, however setting it outside the definition (sound.looping = true) works as intended.

I've noticed that there are quite a few properties for various widgets that can only be set outside the definition. If this isn't a bug, could someone perhaps explain the justification to designing it this way? And also perhaps note inside the API documentation which properties cannot be defined outside the definition (perhaps some sort of symbol like a star or something).