Custom Query (3933 matches)

The documentation for this function should point out, that the fist call of the registered function is not immediately, but after the specified delay time.

Suggestion: [snip] Remarks Every 250 ms (or time ms) the specified "function" is called. The first call is not immediately, but after that time. Typically used to check for unforeseen errors. For example, you could use adlib in a script which causes an error window to pop up unpredictably.

Example code, showing that the first call is *AFTER* the specified intervall:

$start=TimerInit()

AdlibRegister("TestFirstRun",10*1000)

while 1

if TimerDiff($start) > 40*1000 then ExitLoop

WEnd

MsgBox(0,"The End","After " & Round (TimerDiff($start)/1000,3) & " seconds.")

Func TestFirstRun()

MsgBox(0,"TestFirstRun",Round (TimerDiff($start)/1000,3) & " seconds.",1)

EndFunc

When the called dll function is working for a long time, GUI window title sets to "Not responding" and it stops interacting with a user. Only when the function exits, the interface starts working properly.

When i use dllCall with a C dll return a error 6 with SetupDiEnumDeviceInfo. But if i use same dll with a C software it work. Attache examples.