You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is caused by the wait_finished signal not being emitted with certain tags.
This seems to be because the last variable in bbcodeWait.gd is never equal to length - 1, thus line 27 is never reached.
Forcing the skip by pressing the skip button lets me advance. There might be a clue there.
I noticed this bug with a couple of dialogues in the bbcode example. Specifically, the ones that have the [lb] tag, so it definitely has something to do with that.
I'm not sure how to fix it myself, but I hope this info can help!
The text was updated successfully, but these errors were encountered:
Yep this is a known issue (first one mentioned in README.md). I think the fix for this issue is probably a rewrite of the bbcodewait.gd file. I plan to do this as soon as I get some free time. So stay tuned!
Just found this when using the current demos - the ExampleBBCodes demo breaks and doesn't show the OK buttons to progress because bbcodeWait.gd gets stuck looping never reaching what it think is the final character (char 67). Did a bunch of debugging to see if I could fix it for you but eventually found your FIXME comment at
# FIXME : Length calculation is borked when the value has [, ] unrelated to any bbcodes.
Seems like _update_wait_tags is maybe the true fix? bbcodewait's _process_custom_fx is simply acting on what seems like the wrong last dict entry value that was fed to it.
The issue is caused by the
wait_finished
signal not being emitted with certain tags.This seems to be because the
last
variable inbbcodeWait.gd
is never equal tolength - 1
, thus line 27 is never reached.Forcing the skip by pressing the skip button lets me advance. There might be a clue there.
I noticed this bug with a couple of dialogues in the bbcode example. Specifically, the ones that have the
[lb]
tag, so it definitely has something to do with that.I'm not sure how to fix it myself, but I hope this info can help!
The text was updated successfully, but these errors were encountered: