Custom Query

Hi,

I'm not sure if this is an intended behaviour or a bug. GUICtrlCreateGraphic since it doesn't use a window handle it creates the grapthic on the last GUI created; if that GUI was deleted GUICtrlCreateGraphic will fail.

Here is a sample script; it might not be the best example but it shows the above behaviour. Once the last GUI was deleted GUICtrlCreateGraphic will always return 0.

Maybe a future release might consider using a window handle in GUICtrlCreateGraphic call?

Thank you

{{{#include <GUIConstantsEx.au3>

GUICreate("1", 200, 200, 100) $but2 = GUICtrlCreateButton("Create Gr Success", 20, 170, 160, 25) GUISetState() GUICreate ("2", 200, 200, 310) GUISetState() $but = GUICtrlCreateButton("Create Gr Fail", 20, 170, 160, 25) $gg = GUICreate ("3", 200, 200, 520) GUISetState()

Do

$msg = GUIGetMsg()

If $msg = $but Then

GUIDelete($gg)

$a = GUICtrlCreateGraphic(20, 50, 100, 100) GUICtrlSetBkColor(-1, 0xffffff) GUICtrlSetColor(-1, 0)

GUICtrlSetGraphic(-1, $GUI_GR_COLOR, 0xff0000, 0xff0000) GUICtrlSetGraphic(-1, $GUI_GR_PIE, 50, 50, 40, 30, 270)

GUICtrlSetState(-1, $GUI_SHOW) MsgBox(0, "return", "Return code GUICtrlCreateGraphic "&$a, 2)

EndIf If $msg = $but2 Then

$b = GUICtrlCreateGraphic(20, 50, 100, 100) GUICtrlSetBkColor(-1, 0xffffff) GUICtrlSetColor(-1, 0)

GUICtrlSetGraphic(-1, $GUI_GR_COLOR, 0xff0000, 0xff0000) GUICtrlSetGraphic(-1, $GUI_GR_PIE, 50, 50, 40, 30, 270)

GUICtrlSetState(-1, $GUI_SHOW) MsgBox(0, "return", "Return code GUICtrlCreateGraphic "&$b, 2)

EndIf

Until $msg = $GUI_EVENT_CLOSE }}}

I know that page faults are not errors per se, but ProcessExists() is really inducing loads of them and it seems to be the only function to do so (~155 page faults per call). The following code generates 10000+ page faults per second:

While 1
	ProcessExists("Anything.exe")
	sleep(1)
WEnd

It there some problem with the way the dll is called to get current process information? Does it translate into a higher than required CPU usage?

The program I am trying to automate appears to use the directx high res mouse input for control. Autoit seems to send the same relative data when moving even though the absolute mouse position is correct. To reproduce the problem use the program Future Pinball and press F11 to get into manual camera mode in full screen and then use autoit to create a mouse motion to attempt to center the pinball table on screen. Autoit will move the table in the same direction regardless of what coordinates are scripted for the movement. Only the mouse motion duration/speed effects the distance the camera is moved but not direction. Real mouse movement can properly center a table. hyperlinks references removed due to spam filter.