Custom Query

Hi,

I tested this script and my Windows hung up after I clicked the trayicon and closed the script in Scite.

Sometimes the edit pane is visible, sometimes not. If it is, the behaviour described above happens. I know this is not a "bug", cause I assume that I do use the GuiCreate Func wrong, but I nevertheless wanted to share the info.

#include <EditConstants.au3>
#include <WindowsConstants.au3>
#include <GUIConstantsEx.au3>
$n_studi_gui = GUICreate("Nach Studienzeit", 950, 720, @DesktopWidth / 2 - 475, @DesktopHeight / 2 - 360, $WS_border, Default)
GUICtrlCreatePic(@ScriptDir & "\Bilder\Nach.jpg", -1, -1, 950, 720, $ws_disabled)
$n_studi_zurueck = GUICtrlCreateButton("zurück", 800, 600, 140, 80, 0)
$n_studi_button1 = GUICtrlCreateButton("Tätigkeiten", 50, 25, 175, 50)
$n_studi_button2 = GUICtrlCreateButton("Verdienst", 50, 75, 175, 50)
$n_studi_button3 = GUICtrlCreateButton("Weiterbildungsmöglichkeiten", 50, 125, 175, 50)
$edit = GUICreate(400, 10, 500, 400, $WS_POPUP, Default, $n_studi_gui)
$n_studi_edit = GUICtrlCreateEdit('', 500, 10, 400, 500, Default);BitOR($WS_HSCROLL, $WS_VSCROLL, $ES_READONLY))
GUICtrlSetFont(-1, 10, "", "", "Comicsan MS")
GUISetState(@SW_SHOW, $n_studi_gui)
GUISetState(@SW_SHOW, $edit)

While 1
	$msg = GUIGetMsg()
	If $msg = $GUI_EVENT_CLOSE Then ExitLoop
WEnd
GUIDelete()

Mega

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?