Very minor 0.9.4 issue with same-named game.attributes

DrGlickert

I had a boolean attribute and wanted to change over to an integer attribute.

I named the exactly the same, and started to change over the actors that had the boolean to the integer version.

When I run the game, not having changed all the booleans/integer attributes yet, the game seems to have a "hic-up" and stalls for a second when that/those attributes are used.

It used to be fine in 0.9.3.

This is a minor issue, as I deleted the boolean attribute and now the game runs smoothly again.

Just keep that in mind when you're naming your game.attributes folks!

gyroscope

Hi DrGlickert, I'm wondering if this is a conscious decision by a GS programmer; I guess it's a choice whether or not to give the capability of doing that. And I would have thought that if you double up like this many times, you could be heading for confusion! A suggestion, an integer att. called ThisOne, the boolean version called ThisOneB. :-)

DrGlickert

Yeah, it took me a few minutes to figure out what was going on. It was weird to see that hic-up and then it wouldn't work correctly... it was just weird. Then, when I went to delete the boolean-attribute I saw that all the actors that referenced the integer attribute (not the boolean attribute) were displayed as actors that referenced the boolean attribute.

It can get very confusing if you name attributes the same. I'm sure most people (if any) will not have this problem.

Yodapollo

Thanks for pointing this out. I've passed this issue on to the QA team for review and diagnosis. Thanks!

--Yodapollo