DisplayText doesn't consistently respect Visibility -[ BUG ]-
pHghost
London, UKMember Posts: 2,342
When an actor has a DisplayText behavior in it and its Visibility is set to false, the text correctly doesn't display.
But if an actor starts with Visibility set to true, and then it is changed later on (for example by click), the displayed text stays behind, even though the actor itself stops being visible.
How to reproduce:
1) Create an actor with single DisplayText behavior. Drop on scene three times.
2) Edit two of the actors. In the first, change Visibility to false. In the second, create a rule, which will change Visibility to false after clicking on it. Leave the third the way it is.
3) Run in Creator Preview or as ad-hoc on device.
4) Click (tap) second actor.
5) Compare results.
I've created a bug entry for this problem: http://bugs.gamesalad.com/show_bug.cgi?id=1274
There is a sample project attached for anyone wishing to play around with it.
Comments
@BlackCloakGS @GeorgeGS
Changing 'Visible' while DisplayText is displaying text seems to be the culprit. It 'freezes' the text on screen, and will do so repeatedly, layering uncleared text on top of itself.
If you:
1) Make an actor with a rule, when pressed, it Displays text, and leave Otherwise empty,
when you touch the actor, it will show the text, if you don't touch it, the text disappears. If you:
2) Add a make Visible false right before the DisplayText,
when you touch the actor, it will show nothing, disappearing, as should happen. BUT, if you:
3) Move the make Visible false AFTER the text,
not only will the text appear (it shouldn't, with Visible set to false), but it will in fact stay displayed, stuck on the screen, even when you stop touching the actor.
Updated project file attached, newly described behavior in actor in lower row.
Anyone at GameSalad HQ seeing this?
@BlackCloakGS @GeorgeGS
If you submitted a bug report they've either seen it or its in the queue. Bugs aren't always responded to the same day.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
OK, I'll wait a bit. Usually, when submitting a bug in the database, I got initial responses quite quickly, though not this time, so I was worried it might have fallen through.
I suspect it's just a very very low priority (as it should be considering how easy it is to work around).
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
@Armelline I haven't found any way to work around it, except not using DisplayText, and pre-rendering all text which will be in a project, which isn't really a workaround, as you lose dynamic reactions to things like table values etc.
Its a bug that I have not had time to fix. The work around is have the actor visibility set to true then have the first behavior in the actors set the visibility to false. Then after that the visibility setting should work.
If you can see the bug in the database we can too.
It takes time to confirm the issue in-house and then it goes on the list of things to fix.
@pHghost Sorry you're correct, this bug is much worse than it looked from your first post. I hadn't seen your second project example.
It's not just a bad bug, it's darn weird.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
@BlackCloakGS Thanks! I'll test that out when I get home.
Yes, it is weird. Don't know how to explain it, there is some strange code interplay somewhere.
Nope, the text is still getting stuck on screen.
ok I will look into the bug
Thanks!