|
Nattie Apprentice
Joined: 24 Jul 2008 Posts: 109
|
Posted: Wed Aug 06, 2008 4:45 am
[2.34, 2.35] Gauge not refreshing properly |
I have a gauge that counts down how many seconds I have until I am able to perform another action. It's pretty simple; the seconds are stored in the variable @t, and lots of other scripts and such use the information from that variable as well.
The value and caption of my gauge are @t. (The max value on the gauge is @tmax, which is how many seconds are initially read in. Every time the game tells me how long I must wait, @t starts equal to @tmax and then @t counts down once each second until it hits zero.)
This gauge worked perfectly, always displayed properly, etc, until I upgraded to 2.34. Same problem persists in 2.35. I've waited to post about it in hopes that I could figure out if there's a pattern to when it stops workig, but I haven't yet found one. So, problem as follows:
The gauge will randomly quit refreshing properly. The variable itself is working properly because doing a #SHOW @t shows it counts down, and all my scripts that take into account @t have no problems with it. It usually freezes somewhere in the middle -- like on 7 -- but not always. Sometimes it freezes on 0. Sometimes it will freeze on some second, and stay frozen until it hits zero, at which point it will display 0 but then no longer update. Sometimes it just stays frozen on the same second indefinitely. Sometimes it will stay frozen for several minutes and then tick to the current number and freeze again.
Sometimes enabling and disabling the gauge will fix it. Sometimes it does not. Sometimes it fixes it for a few cycles and then it freezes again.
Clicking on the gauge -- which is not assigned to any script -- will refresh it to whatever the current second is, but it will stay frozen until I click it again. So, for example, if it freezes and I spam-click the gauge, it will count down jerkily, but it's still frozen if I stop clicking it.
I tried uninstalling and reinstalling under both 2.34 and 2.35. Neither made a difference. :-/ |
|
|
|
Tech GURU
Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Wed Aug 06, 2008 5:56 am |
Have you tried deleting and recreating the gauge.
|
|
_________________ Asati di tempari! |
|
|
|
Nattie Apprentice
Joined: 24 Jul 2008 Posts: 109
|
Posted: Wed Aug 06, 2008 6:27 am |
Yup. :-/
|
|
|
|
Arde Enchanter
Joined: 09 Sep 2007 Posts: 605
|
Posted: Wed Aug 06, 2008 7:36 am |
May be you have duplicated @t variable somewhere in your package? Try Ctrl-F in the package editor for "t" variable name
|
|
_________________ My personal bug|wish list:
-Wrong Priority when copy-paste setting
-1 prompt trigger for Mapper, Session and General Options, not 3 different!
-#SECTION can terminate threads
-Buttons can't start threads |
|
|
|
Nattie Apprentice
Joined: 24 Jul 2008 Posts: 109
|
Posted: Wed Aug 06, 2008 8:27 am |
There's only the one t variable. :-/
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Aug 11, 2008 5:30 pm |
You'll need to export the button and script to an XML file and then post the XML here within [CODE] tags so that we can try it. I'm not aware of any change made in v2.34 that would cause this and all of my buttons are updating just fine here.
|
|
|
|
|
|