layer Posted October 9, 2005 Share Posted October 9, 2005 (edited) Hey fellas... I've written a couple of _IsFunctions just now, I did it really fast, so I don't know if they work or not, because I didn't test them. So if anyone want's to test them, feel free. Some may be completley useless, others may be like gold. You tell me Removed for now. Edited October 10, 2005 by layer FootbaG Link to comment Share on other sites More sharing options...
Guest Mixture63 Posted October 10, 2005 Share Posted October 10, 2005 Hey fellas... I've written a couple of _IsFunctions just now, I did it really fast, so I don't know if they work or not, because I didn't test them. So if anyone want's to test them, feel free. Some may be completley useless, others may be like gold. You tell me expandcollapse popupFunc _IsChild($hWndParent, $hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsChild", "hwnd", $hWndParent, "hwnd", $hWnd) Return $v_Call[0] EndFunc Func _IsHungAppWindow($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsHungAppWindow", "hwnd", $hWnd) Return $v_Call[0] EndFunc Func _IsWindow($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsWindow", "hwnd", $hWnd) Return $v_Call[0] EndFunc Func _IsWindowUnicode($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsWindowUnicode", "hwnd", $hWnd) Return $v_Call[0] EndFunc Func _IsWindowIconic($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsWindowIconic", "hwnd", $hwnd) Return $v_Call[0] EndFunc Func _IsZoomed($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsZoomed", "hwnd", $hwnd) Return $v_Call[0] EndFunc Func _IsWindowVisible($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsWindowVisible", "hwnd", $hwnd) Return $v_Call[0] EndFunc Func _IsGUIThread($bConvert) Local $v_Call = DllCall("user32.dll", "int", "IsGUIThread", "int", $bConvert) Return $v_Call[0] EndFunc Func _IsMenu($hWnd) Local $v_Call = DllCall("user32.dll", "int", "IsMenu", "hwnd", $hWnd) Return $v_Call[0] EndFuncMe likes. It's very good that you've done this and I suggest you prep it to be used as a standard include in the next release of AutoIt.Who's encharge of that Jdeb? Link to comment Share on other sites More sharing options...
layer Posted October 10, 2005 Author Share Posted October 10, 2005 (edited) Me likes. It's very good that you've done this and I suggest you prep it to be used as a standard include in the next release of AutoIt.Who's encharge of that Jdeb?Heh, thanks. Some of them like the GUIThread one probably can't even be useful in AutoIt, but who knows. And some of them, I think are already built in functions. But I really like the _IsHungAppWindow , I think that could be useful. And a few others. I'll see what I can do.And yes, JdeB is incharge for the UDF's. Edited October 10, 2005 by layer FootbaG Link to comment Share on other sites More sharing options...
Valik Posted October 10, 2005 Share Posted October 10, 2005 What happens if one of these functions fail? I can virtually guarantee that IsGUIThread will fail for a ton of people and so will IsHungAppwindow. Link to comment Share on other sites More sharing options...
Guest Mixture63 Posted October 10, 2005 Share Posted October 10, 2005 What happens if one of these functions fail? I can virtually guarantee that IsGUIThread will fail for a ton of people and so will IsHungAppwindow.We will just have to test them all on different peoples' computers then won't we now? Link to comment Share on other sites More sharing options...
layer Posted October 10, 2005 Author Share Posted October 10, 2005 We will just have to test them all on different peoples' computers then won't we now?No no, Valik's right. I probably shouldn't have posted this until I did valid error checking. I'll either add it tonight or tomorrow. FootbaG Link to comment Share on other sites More sharing options...
Guest Mixture63 Posted October 10, 2005 Share Posted October 10, 2005 No no, Valik's right. I probably shouldn't have posted this until I did valid error checking. I'll either add it tonight or tomorrow.FINE!!!! THEN I WANT TO BE LEFT!!!!!Is that ok with you? Link to comment Share on other sites More sharing options...
Valik Posted October 10, 2005 Share Posted October 10, 2005 We will just have to test them all on different peoples' computers then won't we now?There's no need to test anything. Look at the "Minimum Operating System" on MSDN for each of these functions and you will see the answer immediately. If some of the functions fail, I think thats probably the least of your concerns since it will entail a catastrophic failure in the operating system (Some functions are available on every version of Windows AutoIt runs on). However, some of these functions do not exist on certain versions of Windows and that is a perfectly normal situation. Link to comment Share on other sites More sharing options...
Guest Mixture63 Posted October 10, 2005 Share Posted October 10, 2005 There's no need to test anything. Look at the "Minimum Operating System" on MSDN for each of these functions and you will see the answer immediately. If some of the functions fail, I think thats probably the least of your concerns since it will entail a catastrophic failure in the operating system (Some functions are available on every version of Windows AutoIt runs on). However, some of these functions do not exist on certain versions of Windows and that is a perfectly normal situation.O.Well, maybe he could cut out a few functions, and only use the ones that are guaranteed to work. 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