| Author |
Message |
Forum: Support Topic: VarSetCapacity & DllCall - Unexpected Results |
| kimballd |
|
Posted: January 24th, 2008, 5:22 am
|
|
Replies: 9
Views: 561
|
| There was definately a bug in my code, and it was unintentional. Logically, the code I included above should not have worked. The fact that it did work is why I posted in the forum. My worry is that one of the functions, specifically VarSetCapacity, isn't functioning as expected, or at least, as doc... |
|
 |
Forum: Support Topic: VarSetCapacity & DllCall - Unexpected Results |
| kimballd |
|
Posted: January 20th, 2008, 9:07 am
|
|
Replies: 9
Views: 561
|
| I have "successfully" run the following code millions of time over, only to have it fail on me today when I copied this snippet to another script. FYI: Identify.exe is part of the ImageMagick utility suite. "ImagePath" contains the absolute path to an image. CMD = cmd /c Identify... |
|
|
Forum: Support Topic: CMDret (dll version) RunWEx return limitation |
| kimballd |
|
Posted: July 20th, 2007, 7:02 pm
|
|
Replies: 6
Views: 1568
|
| RunWEx is working great on the test version. I ran two different tests, one with 28,000 chars and another with 1,570,000 chars, and both ran as expected. In my earlier tests, RunReturn didn't seem to have the issue, but it might be good to take a look at the code anyway, just in case. Thanks for yo... |
|
|
Forum: Support Topic: CMDret (dll version) RunWEx return limitation |
| kimballd |
|
Posted: July 9th, 2007, 5:08 pm
|
|
Replies: 6
Views: 1568
|
|
|
Forum: Support Topic: CMDret (dll version) RunWEx return limitation |
| kimballd |
|
Posted: July 4th, 2007, 8:26 pm
|
|
Replies: 6
Views: 1568
|
|
|
Forum: Support Topic: CMDret (dll version) RunWEx return limitation |
| kimballd |
|
Posted: July 3rd, 2007, 11:46 pm
|
|
Replies: 6
Views: 1568
|
| In using the DLL version of CMDret , namely the RunWEx function, I've had problems getting more than 4000 characters to be returned. RunReturn doesn't seem to have this issue. Example: ;for Comparison RunWait, cmd /c dir c:\windows >output1.txt ;RunWEx CMD = cmd /c dir c:\windows VarSetCapacity(... |
|
|
Forum: Scripts Topic: Code to convert from/to UNIX timestamp. |
| kimballd |
|
Posted: September 9th, 2005, 11:38 pm
|
|
Replies: 21
Views: 8479
|
| Well toralf , here is that extra complication you were "looking" for: A true Unix Timestamp is based off of Coordinated Universal Time (UTC) time (which is relatively close to Greenwich Mean Time (GMT)). Thus, the code could easily be edited to this: T = %A_NowUTC% T -= 19700101000000,seconds The co... |
|
|
Forum: Support Topic: Using GUI Returns within a Loop |
| kimballd |
|
Posted: April 15th, 2005, 9:43 pm
|
|
Replies: 9
Views: 946
|
| I was worried my previous explanation wouldn't cut it. Here is an expanded example that uses GoTo where I would like to use a Loop. ;-------------------------------------------------------------- ; Initialize Variables ; loopcount = 1 EditboxTextCount = 0 ; ;-----------------------------------------... |
|
|
Forum: Support Topic: Using GUI Returns within a Loop |
| kimballd |
|
Posted: April 15th, 2005, 8:05 pm
|
|
Replies: 9
Views: 946
|
| In this code example, the "return" that is used to wait for user input via the GUI also breaks the Loop. It creates an error message when it comes to the "}" stating that there was an "unexpected end-of-block". Loop { Gui, add, text,,loop begun Gui, add, button,default, &ADD Gui, show retur... |
|
|
Forum: Suggestions Topic: MsgBox Options |
| kimballd |
|
Posted: January 11th, 2005, 8:30 pm
|
|
Replies: 2
Views: 959
|
| Currently, the "options" variable in the MsgBox command cannot accept variables. In other words: msgboxoption=4096 msgbox, %msgboxoption%, Title, Hello, Dave. returns a msgbox that contains the text: 4096, Title, Hello, Dave. instead of a system modal box displaying the text: Hello, Dave. Is there a... |
|
|
| Sort by: |
Login
Register
FAQ
Search