Custom Query

in every "set time format miliseconds" there is missing a "l" => milliseconds! So the format is never set to MS

TestScript: (test only with .wav, because "time format bytes" dosn´t work with .mp3)

#include <Sound.au3>
$aSnd = _SoundOpen(@ScriptDir & "\Test.wav")
$iDuration = _SoundLength($aSnd);correct because milliseconds is the standard format
ConsoleWrite("+ Duration: " & $iDuration & @CRLF)

__SoundMciSendString("set " & $aSnd[0] & " time format bytes")
$iDuration = _SoundLength($aSnd);returns bytes, because "set time format" fails inside this function
ConsoleWrite("! Duration: " & $iDuration & @CRLF)

__SoundMciSendString("set " & $aSnd[0] & " time format milliseconds")
$iDuration = _SoundLength($aSnd);correct again
ConsoleWrite("+ Duration: " & $iDuration & @CRLF)

E

there are still a lot of DllCall´s where "ptr" is used. e.g. _WinAPI_UpdateLayeredWindow or _WinAPI_WaitForMultipleObjects

I think that it is no problem to change every "ptr" (except return type ;)) to "struct*", so the User can pass a struct directly without DllStructGetPtr.

thx

Before you whack this request for a GoTo, let me explain... Consider a stack of a couple hundred records, with 50 elements in each. In a loop, pull 1 record and perform 70+ transforms on various parts of the record, including feeding data to an external application after each transformation. When done, get the next record and repeat.. all well and good, nothing new here. Now, consider the following issue: at any point in the processing, the external application can throw up a "Bad data" box. I am catching that event Via Adlib() So, Error box caught.. and, because this means the Data is bad, I can NOT process this record any more. So how do I abort the record? There is no way to "On condition, branch to the end of the loop"

The consensus in the forums is that, before each and every single statement in the loop, I have to add an "If $Abortcode="false" then condition. For 3 or 4 statement loops, that's fine, but for 70+ steps, with an average of 10 lines per step, you're talking about adding 700 lines of code. That is a bit much.... So, I am proposing as an extension of If...Ehen... Else If...Then ::Label and ::Label be added as a location marker (If you ever see some idiot use If 1=1 then ::Label, feel free to fry them in oil)