frank10 Posted May 21, 2012 Share Posted May 21, 2012 As sometimes I look at some code to translate to autoit using DllCall, ObjCreateInterface, AutoitObject, DllStructCreate and so on... Which are the parts that can't absolutely be translated? For example, vectors like this? vector< cv::Rect > faceVec; detectScale( faceVec ); and what else? Link to comment Share on other sites More sharing options...
Zedna Posted May 24, 2012 Share Posted May 24, 2012 As far as I know Classes can't be used for example GDI+ ones: http://msdn.microsoft.com/en-us/library/ms533958%28v=vs.85%29 Also multithreading can't be done (natively and simply). Also look here http://www.autoitscript.com/trac/autoit/wiki/AutoItNotOnToDoList Resources UDF ResourcesEx UDF AutoIt Forum Search Link to comment Share on other sites More sharing options...
frank10 Posted May 25, 2012 Author Share Posted May 25, 2012 At least OO is quite present now through Autoit_Object. Maybe also don't work some types with DllCall, for example receive a structure as a return type, ie: (as a struct type CvScalar) CvScalar cvScalar(double val0, double val1 CV_DEFAULT(0), double val2 CV_DEFAULT(0), double val3 CV_DEFAULT(0)) can't work as: DllCall($cvCore_dll, ' ??? :cdecl','cvScalar', 'double','10', 'double','0', 'double','0', 'double','0') ; Is there some plans to make better DllCall and structs? Or generally integration with C? 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