Erke Posted January 24, 2016 Share Posted January 24, 2016 you should really null check that widget before calling its isVisible(). incase you think you did. I have to tell you, you didn't. stuff if the widget is null he'll break the loop, means the code will never reach "if (w.isVisible())". Quote Link to comment Share on other sites More sharing options...
Joseph Posted January 24, 2016 Share Posted January 24, 2016 (edited) if the widget is null he'll break the loop, means the code will never reach "if (w.isVisible())".No offense but I know what I'm talking about......I got this off of google...If u have used multiple if statements then if the condition is true all will be executed and if u have used if and else if combination only one will be executed where first comes the true value Second, break statements are used to break loops for example a while loop, for loop, do while loops. What he has there is probably under the onLoop and the onLoop isn't really a loop statement like I posted above, but rather an int method that just ge re looped by the client.......... Edited January 24, 2016 by Joseph Quote Link to comment Share on other sites More sharing options...
Erke Posted January 25, 2016 Share Posted January 25, 2016 No offense but I know what I'm talking about...... I got this off of google...If u have used multiple if statements then if the condition is true all will be executed and if u have used if and else if combination only one will be executed where first comes the true value Second, break statements are used to break loops for example a while loop, for loop, do while loops. What he has there is probably under the onLoop and the onLoop isn't really a loop statement like I posted above, but rather an int method that just ge re looped by the client.......... No offense but you weren't sending that signal... Quote Link to comment Share on other sites More sharing options...
