DaveF Posted December 19, 2005 Posted December 19, 2005 Hi DaveF-The bad thing was that both were version 97. If I ran it through Scite it failed. If I ran it through START>PROGRAMS>AUTOIT3>BETA>RUNSCRIPT it worked... Why would this be different? Well... To answer the question that you're asking, when run from SciTE the AutoIt EXE and your script are given valid pipes to a console for writing messages and errors and those are connected (indirectly) to the SciTE output window. When AutoIt3.exe or a compiled script are run from the Windows shell by shortcut or double-click or whatever those pipe connections don't exist; Windows sees that AutoIt is what it considers a "Windows" app (as opposed to a console app) and judges that it doesn't need them. Would this make a difference? In this case I don't know. In bringing up the @AutoItVersion macro had intended to suggest that you can put a debug popup in your script to verify that it really is the beta version 3.1.1.97 EXE that's being run when you do your tests. What happens when you compile your script with beta 97? Yes yes yes, there it was. Youth must go, ah yes. But youth is only being in a way like it might be an animal. No, it is not just being an animal so much as being like one of these malenky toys you viddy being sold in the streets, like little chellovecks made out of tin and with a spring inside and then a winding handle on the outside and you wind it up grrr grrr grrr and off it itties, like walking, O my brothers. But it itties in a straight line and bangs straight into things bang bang and it cannot help what it is doing. Being young is like being like one of these malenky machines.
jefhal Posted December 21, 2005 Author Posted December 21, 2005 What happens when you compile your script with beta 97?I'll try that at work today. As well as your idea of showing the @AutoItVersion value. Although, I thought the version that Scite shows when it runs a program was the same thing? ...by the way, it's pronounced: "JIF"... Bob Berry --- inventor of the GIF format
Gigglestick Posted December 21, 2005 Posted December 21, 2005 Another option might be to peek at the Stdout before reading it to avoid the "freezing" issue while waiting for data. My UDFs: ExitCodes
jefhal Posted December 22, 2005 Author Posted December 22, 2005 (edited) If you ever have a question about which EXE (or compiled stub) is really running a script you can use the @AutoItVersion macro in a debug MsgBox or whatever to see the version.FINALLY! I finally had time today to run the tests you all had suggested. Here's what I found:1. The script fails if run from Scite using Beta 972. The script succeeds if run from the START menu using: START-PROGRAMS-AUTOIT-BETA-RUN_SCRIPT(BETA 97)3. The script succeeds if I use Scite to compile it (Beta 97) and then run the executable from Windows Explorer.This means that there is something about Scite that is causing a bottleneck or loss of data it appears. By the way, after the script runs in Scite, the Scite control window (bottom of screen) displays 60 copies of the following message from ADFIND:AdFind V01.26.00cpp Joe Richards (joe@joeware.net) February 2005That is, one copy for each loop that ran before it died... Edited December 22, 2005 by jefhal ...by the way, it's pronounced: "JIF"... Bob Berry --- inventor of the GIF format
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now