LxP Posted November 28, 2005 Posted November 28, 2005 Another one of life's little mysteries, I guess.
AutoIT Geek Posted November 28, 2005 Author Posted November 28, 2005 Another one of life's little mysteries, I guess. this IS a flaw in AutoIT, a bug, a misbehave issue. DLLCALL should return the same string as other functions that return handle well, thanx for your help, the issue was cleared im a bit smarter now ( am i ? god knows )
Valik Posted November 29, 2005 Posted November 29, 2005 Forgive me for not knowing anything about the HWND types, it's not like I wrote the code or anything (Since you're stupid, that's more than a hint that I wrote the code for HWND support so I know how it works).An HWND is stored as an HWND. Period. End of story. Internally it's stored as an HWND. It's called an HWND when referenced from the AutoIt language. It's an HWND. Whine, bitch, moan, imagine bugs all you want, it's still an HWND. I don't know what crack-pipe you are smoking which makes you say it's stored as a string. It's not, it's an HWND. HWND HWND HWND. Get it yet? It's an HWND. One more time for the retard, it's an HWND.And for the third time, I changed how HWND's behave since 3.1.1 so yes, there are differences in the behavior. Shut the hell up and move along. Nobody can answer your stupid-ass questions better than I can, I wrote the damn code you're bitching about so piss off unless you can demonstrate a bug in the code, which you have yet to do. You've pointed out some inconsistencies but I really don't understand what the hell you are whining about amongst all your insolence. Until somebody like LxP or virtually anybody else with a brain can post a demonstration of what is happening and what is expected with no conjecture on why its happening, then I'm afraid you're SOL.It's an HWND.
GaryFrost Posted November 29, 2005 Posted November 29, 2005 Walks like a duck, quacks like a duck, must be a duck, or in this case an HWND as i posted earlier, you need to us IsHWnd for beta, as valik pointed out an HWnd is now treated as it should be. SciTE for AutoItDirections for Submitting Standard UDFs Don't argue with an idiot; people watching may not be able to tell the difference.
AutoIT Geek Posted November 29, 2005 Author Posted November 29, 2005 (edited) OK VALIK i got it, its an HWND, fine, i embedded this info in my brain, fixed it hard, GOT IT. heres a question, what is an apple ? a BAD answer would be, "you are an idiot ? AN APPLE IS AN APPLE " a GOOD answer would be, " an apple is a fruit, it grows on a tree, it grows in summer time, there are some kinds of apple so there are different colors and tastes for different apples, some are red and sweet, some are green and slightly sour, ..., ..., ... " we can bash and bitch each other for NO GOOD, its a WASTE OF TIME, im NOT in to it, ok ? i take ALL my BITCHING and INSOLENCE back, it NOT A BUG, i'll stop using CRACK - PIPES, I'LL DO BETTER. can you be kind and supply or publish the source code for HWND's type in autoit, and how autoit handles HWND's ? thank you. P.S. can you please reveal the code for IsHWND() and DLLCALL() for v3.1.1.91 ? Thanks again. Edited November 29, 2005 by AutoIT Geek
AutoIT Geek Posted November 30, 2005 Author Posted November 30, 2005 Why? are you kidding me ?i want to take over the world and THAT code in the only part my evil plan lacks.it IS suppose to be an open source, no ?since i program directly with win API's, and i have the source of v3.1.0 i CAN writemy own DLLCALL() with LoadLibrary() and FreeLibrary() and compile it.i want to check what i am doing wrong in parts of my code. is that a good reason ?
Valik Posted December 1, 2005 Posted December 1, 2005 it IS suppose to be an open source, no ?No, I suggest you look again. AutoIt is more or less closed source in the post 3.1.0 releases.since i program directly with win API's, and i have the source of v3.1.0 i CAN writemy own DLLCALL() with LoadLibrary() and FreeLibrary() and compile it.i want to check what i am doing wrong in parts of my code. is that a good reason ?Not really. I doubt you really have a need for the ability to call DLL functions at run-time with an unknown number/type of parameter(s). It's a non-trivial concept and the usefulness is limited to either being a learning experience or writing a language.I don't see why you're so concerned with this particular function. As I've stated several times, the magic is done via inline assembly. The rest is AutoIt-specific type conversions.
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