ThatGamerBlue Posted September 20, 2017 Posted September 20, 2017 I'm implementing a custom break manager into my script, is it possible (using any way needed) to remove the JOptionPane from showing when you override it. I wouldn't mind but it's blocking until you close it which is annoying for automation purposes.
HeyImJamie Posted September 20, 2017 Posted September 20, 2017 -allow norandoms should work. You'd need to handle your own logins though.
Eagle Scripts Posted September 20, 2017 Posted September 20, 2017 If you want to really do it through overriding the breakmanager, I believe there is no way around the OptionPane as Alek probably wanted to make sure users won't blame OSBot for any false use of the BreakManager Overriding
Alek Posted September 20, 2017 Posted September 20, 2017 13 minutes ago, HeyImJamie said: -allow norandoms should work. You'd need to handle your own logins though. 8 minutes ago, Juggles said: -norandoms is the only way You guys didn't read his post, at all lol. @3qTQlBnsOsyfetvA No, @Eagle Scripts mentioned exactly why. I get lots of bug reports about break manager and autologin as it is, I don't need the added confusion of whether or not it was coming from a custom handler. There was a good suggestion about adding an ignore flag, but believe it or not I would anticipate still false reports. It's something I haven't forgot about. 2
ThatGamerBlue Posted September 20, 2017 Author Posted September 20, 2017 (edited) @Alek damn, maybe you could add an override as a cli option? maybe -allow randomoverride or similar Edited September 20, 2017 by 3qTQlBnsOsyfetvA
Alek Posted September 20, 2017 Posted September 20, 2017 24 minutes ago, 3qTQlBnsOsyfetvA said: @Alek damn, maybe you could add an override as a cli option? maybe -allow randomoverride or similar Read above lol
ThatGamerBlue Posted September 20, 2017 Author Posted September 20, 2017 (edited) 35 minutes ago, Alek said: Read above lol I read it but I was thinking burying it in the CLI would stop the false reports because the only people who'd use it are people who knows what it does. edit nvm im retarded, it'd still be a nice thing tho Edited September 20, 2017 by 3qTQlBnsOsyfetvA
HeyImJamie Posted September 21, 2017 Posted September 21, 2017 4 hours ago, Alek said: You guys didn't read his post, at all lol. @3qTQlBnsOsyfetvA No, @Eagle Scripts mentioned exactly why. I get lots of bug reports about break manager and autologin as it is, I don't need the added confusion of whether or not it was coming from a custom handler. There was a good suggestion about adding an ignore flag, but believe it or not I would anticipate still false reports. It's something I haven't forgot about. Wut. He said by using any method at all 1
ThatGamerBlue Posted September 21, 2017 Author Posted September 21, 2017 (edited) solved public class PaneRemover extends Thread { public void run(){ boolean pane = false; while(!pane) { try { Window[] windows = Window.getWindows(); for (Window window : windows) { if (window instanceof JDialog) { JDialog dialog = (JDialog) window; if (dialog != null && dialog.getTitle().equalsIgnoreCase("Override Warning!")) { Main.main.log("found pane"); pane = true; dialog.dispose(); } } } } catch (Exception e){ } } } } messy but it works Edited September 21, 2017 by 3qTQlBnsOsyfetvA