Richard Robertson Posted February 15, 2008 Share Posted February 15, 2008 I don't have any reason to debug the AutoIt executable, but I would like to debug the plugin I am writing, while it is being run from AutoIt. I attempted to attach Visual Studio to the AutoIt executable but got a message about EULA violation by reverse engineering. Am I pretty much screwed here? Link to comment Share on other sites More sharing options...
Valik Posted February 15, 2008 Share Posted February 15, 2008 Yep, you're pretty much screwed. I seldom write code *inside* AutoIt anymore. I normally write my classes/functions outside AutoIt, get them working in a test application, then hook them up inside AutoIt. I imagine you can do similar. Just write traditional C++ functions to test with, then provide thin AutoIt plugin compatible wrappers around your (presumably inlined) functions. I mean, it shouldn't really matter the source of input as long as you get the expected input. Link to comment Share on other sites More sharing options...
Richard Robertson Posted February 15, 2008 Author Share Posted February 15, 2008 I already started writing the actual code outside of the plugin functions, and then the PLUGIN_DEFINE'd functions just called the other items. Thanks for that though. I didn't think to run them outside the original space. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now