Custom Query (3933 matches)
Results (445 - 447 of 3933)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #570 | No Bug | AutoIt problems handling filenames with two or more consecutive dollar signs | ||
| Description |
Ihave used functions FileGetLong and FileGetTime and both gives error back if filename contains several consecutive dollar signs. Example of filenames giving error: cbep$$bnk.txt
Works for filenames: cbep$bnk.txt
The filename cbep$$bnk.txt comes from (via FTP) an UNISYS Clear Path mainframe machine causing problems in my PC when trying to set the correct modification time with an AutoIt script. |
|||
| #2870 | No Bug | AutoIt send key combinations do not work sometimes | ||
| Description |
When AutoIT is used to copy and paste several hundred lines of text from a text file, line by line (each line will be copied to clipboard using clipput() and inserted into an application using ctrl-v). Sometimes, v or v will be paste into the active window instead of the actual contents of the clipboard being dumped as is specified when send ("v")or ctrlsend is used. |
|||
| #1447 | No Bug | AutoIt timesout on winwait when run by Microsoft Deployment Toolkit 2008 | ||
| Description |
I have a couple AutoIt software installation scripts that timeout when run by a Microsoft Deployment Toolkit task sequence. The command that fails is WinWait($title, $text, $timeout) It will timeout even though the window it is waiting for exists. WinGetTitle("[ACTIVE]", "") returns the title of the window WinGetText("[ACTIVE]", "") returns the text of the window If I take the first window out of the main script and add it to the AdlibRegister("unexpected") function, the window is found and dealt with but then the script times out while waiting for the next window. If I run the script manually while the Microsoft Deployment Toolkit is running, it also times out. If I run the script manually when the toolkit isn't running it runs like it is supposed to. Sometimes I can kickstart the script by jiggling the mouse. I tried using an AutoIt script that jiggles the mouse; it didn't help. The deployment toolkit runs TsProgressUI.exe which displays a progress bar on top of all other windows. This may be what is causing a conflict with AutoIt. I tried to find another bug report on this but didn't. I did find one other user with what sounds the same problem in the forums but the was no answer; probably because he didn't give very much info. http://www.autoitscript.com/forum/index.php?showtopic=97308&st=0&p=699510&hl=mdt&fromsearch=1&#entry699510 |
|||
