Zugg Software :: View topic - Gauges Not Updating Properly from Record Variable

Posted: Wed Oct 26, 2005 12:37 am

I use a record variable to store the information captured from my prompt (health, mana, and movement). I then have 3 gauges set up to display those values.

My problem is that the gauges don't automatically update like they should until I click on something else (i.e. another button or another window), or any other non-record variable updates.

Has anyone else had this problem? Is this normal behavior?

The only 2 solutions I have right now are to split the stats into three variables (which is ok I guess I'd just rather have one variable instead of three), or create some dummy variable thet just bounces between 0 and 1 as part of my prompt trigger to get the gauges to update.
Any other ideas?

Posted: Wed Oct 26, 2005 4:57 am

If you post the actual script for your gauge we may be able to help debug, the gauge can theorectically work with any expresssion and thus should be able to to work with a db record.. But your best bet is to split it. That's standard practice ( and to my knowledge ) there's no issues with that.

I did a quick test using a record and was able to see the value. If you record variables is called Test and the health is stored in HP you would access it via @Test.HP Hope that helps.

Posted: Thu Oct 27, 2005 1:39 am

I included the code the variables for current and max stats, prompt trigger, and 3 gauges below. I used the %db() format in the gauges, but I tested with the @Test.HP format, and got the same results.

Posted: Thu Oct 27, 2005 4:14 am

Ok.. I see the problem. You're using a ',' instead of a '.'; i.e. a comma instead of a period.

@MaxStats.Health
@MaxStats.Mana
@MaxStats.Movement

Replace with these and you should be fine.

Posted: Thu Oct 27, 2005 12:31 pm

Thanks, for the reply Tech but I have a couple of questions/comments.

I'm not sure where I'm using comma incorrectly when I should be using a period.
I used the %db(@MaxStats,Health) function to pull the value not the @MaxStats.Health format. I'm assuming that is what you are referring to.

Also, I said in my last post I tried the @Stats.Health format as opposed to %db(), and still got the delayed updating. Admittedly, I only changed the the Stats variable to the @Stats.Health format not MaxStats so I will try changing both tonight.

Posted: Thu Oct 27, 2005 2:43 pm

Yeah.. I guess I should have clarified. You will need to change the Stats variable as well. I saw the @MaxStats variables first so I only spoke to those. Generally speaking to access a particular entry of a record variable you use the dot-notation. You can read more about it here

Posted: Thu Oct 27, 2005 6:18 pm

Posted: Thu Oct 27, 2005 7:29 pm

I stand corrected. I guess I should say that's what I generally use. Laughing

Posted: Thu Oct 27, 2005 11:57 pm

Ok dot notation didn't work either. I'm just going to split Stats into 3 different variables and that should take care of it.

Novice Joined: 29 Oct 2004 Posts: 34

I had this problem too, so you're not alone. For some reason it doesn't check database variables in guages. If I had a toggle button for a database variable and changed it without the button, the button would not update until I interacted with the GUI. I wasn't really sure how to fix that, and guessing it's more of doing with Zmud's coding, and not sure if you can work around anything to fix it.

Posted: Fri Oct 28, 2005 12:54 pm

Hmmm... I thoughtposted a response last night.. but I guess I must have forgot to submit.

Erasmus,

I copied your trigger verbatim in to my zMud copy. A registered version of 7.21 and had no problems with it, whatsoever. First I manually set the values of the Stats record variable. After that, I tried to see it would update based on you trigger prompt and it did.

I'm guessing that you trigger prompt is actually what's causing the problem since it works for me in both the dot-notation and using %db. I suspect that you're trigger prompt is not correctly triggering and as a results your 'Stats' record variable is not being set. Can you post an example of your mud prompt.

Posted: Fri Oct 28, 2005 5:54 pm

The prompt is: 3100h, 1700m, 500v-

I've tested my prompt using the #SHOWPROMPT command, (I'm sure I've tried it on the mud as well but since it didn't work I've done most of the testing offline) and it seems to capture fine. The gauge never updates to reflect the new values.

Example:
After using the code from several posts ago to create the variables, triggers, and gauges I'll do something like

Posted: Fri Oct 28, 2005 7:47 pm

I think what you're seeing is a quirk of offline testing. Not possible for me to test online right now.

It's seems that when record variables are processed offline, the values are updated but their depedents don't immediately recognize it. A problem that doesn't hold true for regular variables. I tried what you said, and only got updates when I clicked the button or went gauge. However if I tried