battleguard Posted November 26, 2017 Share Posted November 26, 2017 (edited) Debugging scripts in osbot is pretty simple once you learn abut debugging localprocesses. Here are the basic steps you will need 1. Add a breakpoint into your local script you have create 2. Set your build output to go to your OSBOT scripts folder 3. Create a debug configuration that starts an application with the entry point of org.osbot.boot 4. Run your configuration (do not debug it) to bring up osbot so your local processes in intellij can see it. 5. log into your account and then you are ready to attach to the local script process through intellij. Once you have attached run your script and you should now be debugging your script so any breakpoints that the code hits will now stop and allow you to see the variables. 6. you can also add watches to quickly look up things without using print lines and make debugging much easier now. 7. if you need to do more complex statements you can use evaluate expression to have multiple lines. Looks like images got deleted from site so to view the gifs that explain each step use this google cache link https://webcache.googleusercontent.com/search?q=cache:zre9YWkp3WsJ:https://osbot.org/forum/topic/133159-using-the-debugger-with-osbot-local-scripts/+&cd=1&hl=en&ct=clnk&gl=us or this imgur link: https://imgur.com/a/smwr5lu Edited February 21, 2019 by battleguard 10 Quote Link to comment Share on other sites More sharing options...
Viston Posted November 26, 2017 Share Posted November 26, 2017 (edited) Ayy, thank you for that young fella @battleguard @TheWind Edited November 26, 2017 by Viston Quote Link to comment Share on other sites More sharing options...
HeyImJamie Posted November 26, 2017 Share Posted November 26, 2017 Good shit Quote Link to comment Share on other sites More sharing options...
TheWind Posted November 26, 2017 Share Posted November 26, 2017 Fantastic! Thank you for this! Quote Link to comment Share on other sites More sharing options...
The Undefeated Posted November 26, 2017 Share Posted November 26, 2017 This is really useful, thank you! Quote Link to comment Share on other sites More sharing options...
Deceiver Posted November 26, 2017 Share Posted November 26, 2017 nice but white theme 1 Quote Link to comment Share on other sites More sharing options...
Butters Posted November 26, 2017 Share Posted November 26, 2017 This is great, thanks Quote Link to comment Share on other sites More sharing options...
The Undefeated Posted November 26, 2017 Share Posted November 26, 2017 13 hours ago, Deceiver said: nice but white theme It's too much like Eclipse. 1 Quote Link to comment Share on other sites More sharing options...
Dab in a Lab Posted September 30, 2018 Share Posted September 30, 2018 After I was done running the debugger, it wouldn't rebuild my jar file and it lost the JDK for the module. Is there a proper way to stop the debugger? My classes all changed to this: https://gyazo.com/31f882c551a2235cf509a487c5d8924b I ended up making a new project and just copy and pasted the code into it. Couldn't figure out how to fix it otherwise Quote Link to comment Share on other sites More sharing options...
Pegasus Posted February 18, 2019 Share Posted February 18, 2019 All other compiled local jar disappeared after I tried this. Quote Link to comment Share on other sites More sharing options...
Pegasus Posted February 19, 2019 Share Posted February 19, 2019 (edited) On 10/1/2018 at 3:21 AM, Dab in a Lab said: After I was done running the debugger, it wouldn't rebuild my jar file and it lost the JDK for the module. Is there a proper way to stop the debugger? My classes all changed to this: https://gyazo.com/31f882c551a2235cf509a487c5d8924b I ended up making a new project and just copy and pasted the code into it. Couldn't figure out how to fix it otherwise I have encountered the same issue. Select "Inherit project compile output path" should help Edited February 19, 2019 by Pegasus Quote Link to comment Share on other sites More sharing options...
