CustomParams

tacroy · Post by **tacroy** » 11 Nov 2008, 21:19

I've noticed there is a "oldCustomParams" field in the editor. Which infers that the is also a new custom params, which looks to be the customParams field in the popup section of the editor in the tile pane.

Looking at the ranch example, it looks like the setCustomParams function inside of the library symbols actually references the "skins" customParams which seem to be the deprecated version (instead of the "tile" customParams)

Is there a complete walk through on how to use the new customParams?

Specifically, I am trying to write the "walk on this symbol and load next room" thingy. However using the "evt.params.tile.customParams != null" condition and trying to access "evt.params.tile.customParams[0]" fails. I assume because it is looking at the OLD "skin" customParams instead of the "new" "tile" customParams?

Hopefully that made sense. Since there is multiple terms and ideas that re-use names, if you could be a bit verbose to be clearer, I would greatly appreciate it.

Thank you!

tacroy · Post by **tacroy** » 12 Nov 2008, 13:08

Let me simplify the question a bit.

In the "ranch" example you use
evt.params.tile.customParams[0]
to get at the customParams that are set on the "skin"

How do I get access to the "tile" customParams that are set in the editor via the tile popup window?

Thanks.

Post by **Bax** » 17 Nov 2008, 08:59

The "new" customParams property is not available yet; as described in the Editor documentation, that property will be used in a future release of OpenSpace. Currently you have to use the "oldCustomParams" field.

tacroy · Post by **tacroy** » 17 Nov 2008, 13:36

Well that certainly explains why it wasn't working.

Is there a timeline for when that will switch? I want to be sure I am not spending a large amount of creating it one way, only to have to switch when a new version is released.

Post by **Bax** » 17 Nov 2008, 13:44

A new version won't be available soon.