msimurin 4 Posted December 23, 2009 Report Share Posted December 23, 2009 When i use checkbox it works perfect in ubot code, soon as i compile it it seems the exe ignores the if and evaluate checkbox false or true part inside. Anyone else experienced this? So for example, i have checkbox that sets ubot to use or not to use decaptcher. Chose by attribute(captcha image) if #decaptchervariable - evaulate = true use - decaptcher this image if #decaptchervariable - evaulate = false use - decode this captcha manually chose by attribute captcha enter text field change chosen attribute to $captcha I tested this inside ubot dev tools with source and it works PERFECT, soon as i compilte it BOOM skips the if parts with evaluate... and just continues clicking on submit information button.... I also noticed if i first click checkbox in compiled bot few times(i guess to warm it up) it works fine, unless i touch this then it simply doesnt work. Quote Link to post Share on other sites
Aaron Nimocks 19 Posted December 23, 2009 Report Share Posted December 23, 2009 I noticed that awhile back. What I think happens is when you open it and it is compiled if you look at what the value of the checkmark is, it is blank. So its not false or unchecked, its blank. If you click it then it will go to true or checked. If you click it again then it will go to false or unchecked. Point being is the error lies in that the checkbox has no value when you just start it up. The way I got around this is just setting the variable that is attached to the checkbox to false or unchecked. Forget what the actual value is supposed to be. If you do that then it will work fine. Quote Link to post Share on other sites
Guest Jim Posted December 24, 2009 Report Share Posted December 24, 2009 The best work-around for this is to change your condition to be Not {#decaptchervariable = True} instead of #decaptchervariable = False. I hope that fixes your problem Quote Link to post Share on other sites
msimurin 4 Posted December 24, 2009 Author Report Share Posted December 24, 2009 The best work-around for this is to change your condition to be Not {#decaptchervariable = True} instead of #decaptchervariable = False. I hope that fixes your problem yeah i think this is the most simple workaround till this is fixed, thanks Quote Link to post Share on other sites
webautomationlab 21 Posted December 24, 2009 Report Share Posted December 24, 2009 Please post bugs in the bug forum so Seth can see them. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.