Custom Query (3927 matches)

#cs ----
	issue: WinGetTitle(...) returning '[SOH]' character, instead of title of target window.
	- $Title = WinGetTitle("classname=<progname>")
	- $Title = WinGetTitle(<progHandle>)
	- (3.2.13.11), WinGetTitle(...), returnData '[SOH]'
	- (3.2.13.10), WinGetTitle(...), returnData '<winTitle>'
#ce ----

Global $TargetApp_FileSpec = ''
Global $TargetApp_ClassName = ''
Global $TargetApp_ClassSpec = ''

Switch 1
	Case 1
		$TargetApp_FileSpec = 'notepad.exe'
		$TargetApp_ClassName = 'Notepad' ;; default windows Notepad.
	Case 2
		$TargetApp_FileSpec = 'calc.exe'
		$TargetApp_ClassName = 'SciCalc' ;; (Calculator Plus)
EndSwitch

$TargetApp_ClassSpec = '[CLASS:' & $TargetApp_ClassName & ']'
ConsoleWrite('$TargetApp_ClassSpec = ' & $TargetApp_ClassSpec & @CRLF)

F1()
ConsoleWrite('-9-' & @CRLF)
Exit 0

Func F1()
	If Not WinExists($TargetApp_ClassSpec) Then
		Run($TargetApp_FileSpec)
		If WinWait($TargetApp_ClassSpec, '', 2) Then
			ConsoleWrite('WinWait(*): OK' & @CRLF)
			F2()
		Else
			ConsoleWrite('WinWait(*) Failed, $TargetApp_ClassSpec = ' & $TargetApp_ClassSpec & @CRLF)
			Exit 1
		EndIf
	Else
		F2()
	EndIf
EndFunc   ;==>F1

Func F2()
	WinActivate($TargetApp_ClassSpec)
	If WinWaitActive($TargetApp_ClassSpec, '', 2) Then
		ConsoleWrite('WinWaitActive(*)1: OK' & @CRLF)
		F3()
	Else
		ConsoleWrite('WinWaitActive(*) Failed, $TargetApp_ClassSpec = ' & $TargetApp_ClassSpec & @CRLF)
		Exit 1
	EndIf
EndFunc   ;==>F2

Func F3()
	Local $TargetApp_Handle
	$TargetApp_Handle = WinGetHandle($TargetApp_ClassSpec)
	ConsoleWrite('$TargetApp_Handle = ' & $TargetApp_Handle & @CRLF)
	
	Local $TargetApp_Title
	ConsoleWrite(@CRLF)
	
	For $i = 1 to 4
		Opt("WinTitleMatchMode", $i) ;; 1=start, 2=subStr, 3=exact, 4=advanced, -1 to -4=Nocase
		ConsoleWrite('WinTitleMatchMode = ' & $i & @CRLF)
	
		$TargetApp_Title = '-'
		$TargetApp_Title = WinGetTitle($TargetApp_Handle)
		ConsoleWrite('1) $TargetApp_Title = ' & $TargetApp_Title & @CRLF)
		
		$TargetApp_Title = '-'
		$TargetApp_Title = WinGetTitle($TargetApp_ClassSpec)
		ConsoleWrite('2) $TargetApp_Title = ' & $TargetApp_Title & @CRLF)
		
		$TargetApp_Title = '-'
		$TargetApp_Title = WinGetTitle("[active]")
		ConsoleWrite('3) $TargetApp_Title = ' & $TargetApp_Title & @CRLF)
		
		ConsoleWrite(@CRLF)
	Next

EndFunc   ;==>F3

Hello,

I'll refer to two different combobox functions which malfunction on Windows 2000 (sp4 2195) and NT 4 (sp6a).

First one is: _GUICtrlComboBoxEx_Create

and probably derivatives (i mean same type of functions). When compiled to run on the above mentioned OSes, the script/exe throws an error on start "Error: _WinAPI_CreateWindowEx: Cannot find window class."

This *does not* happen on Windows XP or 2003.

I found it through my own scripts, but you can reproduce it if you compile the example script under the _GUICtrlComboBoxEx_Create section of AutoIT's .chm help file. and run in on the reported OSes.

Second one is: (the regular) GUICtrlCreateCombo.

Again problem is on Windows 2000 (2195). I was not able to test on NT 4.0 . Here follows example code:

#include <GuiConstantsEx.au3>

Opt('MustDeclareVars', 1)

_Main()

Func _Main()
	Local $msg, $hGUI, $combobox
	
	$hGUI = GUICreate("Title", 250, 173)
	GUICtrlCreateLabel("Label that bugs the app on Win2k:", 2, 3)
	$combobox = GUICtrlCreateCombo("1", 2, 20, 244)
	GUICtrlSetData($combobox, "2|3|4|5")
	GUISetState()
		While 1
        $msg = GUIGetMsg()
        Switch $msg
            Case $GUI_EVENT_CLOSE
                ExitLoop			
			EndSwitch
		WEnd
		
EndFunc

What it does is that the combobox does not drop down at all. If I will comment the line to create label (;GUICtrlCreateLabel("Label:", 2, 3)), it works as expected on XP/2003 and 2000.

A) Search direction: For symmetry, support should be included for:

1. left-to-right, top-to-bottom (default & only current option)
2. right-to-left, top-to-bottom
3. left-to-right, bottom-to-top
4. right-to-left, bottom-to-top

Various software (not just games) use gauges on screen and the ability to efficiently find the top/bottom/left/right extremes of a monochrome area would have high utility.

B) Search using a logical-AND "pixel mask": Accept X and Y dimensions of a pixel mask. Here, a "pixel mask" is an array of pixels in which _all_ pixels must match the target color for the search to terminate. Shade-variation parameter applies. Of course this pixel mask must be smaller in X and Y dimensions than the rectangle of pixels being searched.

Sometimes onscreen gauges have gradations or text superimposed and so erroneous matches are possible and these situations can require complex (and slow) functions to be written to avoid false positive search results. Requiring _all_ pixels within a search rectangle to match the target color will provide an efficient program building block for such applications.

C) Search using a logical-OR "pixel mask": Corollary to (B) only using a logical-OR "pixel mask" and the condition for terminating the search changes to being when _none_ of the pixels in "pixel mask" match the target color. Shade-variation parameter applies.

Note that this yields a _different_ result than the result from a "single pixel at a time" style search.

This is useful for those gauges that taper off or have rounded extremities however, it may _also_ be used to effectively ignore any text or gradations superimposed on a monochrome gauge.