ID:86015
 
Not a bug
BYOND Version:459
Operating System:Windows XP Pro
Web Browser:Chrome 4.0.249.0
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
Winget fails to return true / false to if() statements.


Numbered Steps to Reproduce Problem:

Download and observe the interface names, values, code values inside of Character Create.dm

I left Test2there to show that return tabbing doesn't help the situation.

Code Snippet:

http://www.byond.com/members/Leur/files/TextLib.zip

Expected Results:

true (1) or false (0) to return to if()

Actual Results:

if() acts weird.
huh.png (52 KB)

Does the problem occur:
Every time? Or how often? Everytime
In other games? it's code.
In other user accounts?It's code.
On other computers?again, it's code.

When does the problem NOT occur?

Doesn't not occur.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Unsure.

Workarounds:
A possible work around might be to create variables, give it each buttons return value, and use if() to see if the text matches the variable text.

(Untested the work around)
winget returns "true" or "false" in the case of is-checked so, they are both text values. "true" and "false" would both return 1 in an if()

your code is incorrect it should be in this format;
if(winget(src,"window","is-checked")=="true")
So like...not a bug.
I see what you're saying. Shouldn't it return boolean though?
Nope.
It's a text value, dunno why, but that's what it says in the Skin ref and such.
Thanks for the help. I'll leave this up here though, Just in case they see it and decide to make it boolean. (If possible)
Another question actually how come there is a noticeable delay between pressing the button which calls the verb and displaying the desired data in the end?
winget() data from my experience takes a while to acquire.
When posting your report, the "code snippet" section is supposed to contain an actual readable code snippet that can be looked at on the fly. If you have a demo to offer (which is always a good thing of course) it should go elsewhere in the text of your report.