Large OSds result in reduced button functionality

Forum Archive - from http://theuniversal.net
Locked
User avatar
zaroba
World Owner
World Owner
Posts: 7257
Joined: Fri Oct 10, 2003 11:06 pm
Location: Hereford, PA
Contact:

Large OSds result in reduced button functionality

Post by zaroba »

Software:Universal Client
Version Number:
________________________________________________________________________
Location

________________________________________________________________________
Description:
I don't exactly know what is going wrong here:

I have OSDs for changing the prices of items in a building. They seem to work fine, but the top 2 lines of var changing buttons do not work correctly. The buttons seem to double activate their OSDs and despite this, not show the correct value of the var. Reloading the OSD window will display a number 1 higher then what you left it at.

For example:
Number is 0. Click it once, it shows 1, but if you exit the OSD and go back in, it is really a 2.

Number is 0. Click once, it shows 1, click a 2nd time, it changes to 3. 3rd time, it changes to 5. But if you exit the OSD and go back in, the value will show as 6.

Happens regardless of what the starting number is.
If it starts at 5 and you click once, it will change to 6, but be 7 after reloading the OSD.

The rest of the buttons work fine, it's only the top 2 var changers that don't work. Script seems all in order as well. Doing a search, there is nothing else changing the var's that the button changes, the var is not used anywhere else in the script. The only places it is used is the OSD showing it's value, and 3 lines to change the value. +1, -1, and set to 0.



The script is also cloned for use in a different building, which works fine and has the exact same var changing mechanics.
________________________________________________________________________
Steps to Replicate:
User avatar
zaroba
World Owner
World Owner
Posts: 7257
Joined: Fri Oct 10, 2003 11:06 pm
Location: Hereford, PA
Contact:

Post by zaroba »

found the issue.

turns out ai forgot to change a number in a different script that was made via cloning the one i found the problem in. as a result, hitting the OSD button was running 2 different events and thus changing the var value twice.
User avatar
Mit
Staff
Staff
Posts: 3551
Joined: Sun Sep 21, 2003 10:14 pm
Location: Unknown

Post by Mit »

okeys.. u happy to resolve this as 'not a bug' or is there something specific (and small) you think the script engine could have added to help avoid that? (There are lots of options for debug & code verification tools but they'll have to come later)
Locked