Leaderboard

So long story short: i am writing a AutoIt3 parser and want some feedback from other AutoIt3 users on this. The following seems to be a valid multi-line comment block: #csA B #ceC What would you consider the content of the comment block? 1: A B C 2: A B 3: B Or maybe something else?

It's version 7.2.8.1124 from 2015. Direct download link from the source: http://cdn01.foxitsoftware.com/pub/foxit/reader/desktop/win/7.x/7.2/en_us/FoxitReader728.1124_enu_Setup.exe That was the last version you could opt to use the classic toolbar. Anything after that you're stuck with the Ribbon, Here's the discussion about it on Foxit's forum: https://forums.foxitsoftware.com/forum/portable-document-format-pdf-tools/foxit-reader/152744-need-previous-version-of-foxit-reader-7-2#post152744

With your Foxit Reader method, after loading the PDF desired, have you tried simply sending a Ctrl-a to select all text, then a Ctrl-c to copy it to the clipboard? Then your script can retrieve the copied text with ClipGet and do whatever you want with it (i.e. save it to a file, display it, manipulate it, etc.). This method doesn't require as much faffing about with the menus and controls in Foxit, and it seems to produce cleaner text since it doesn't include all of the extraneous blank lines that the 'Save As' method generates. For a very lengthy document, it might take a few seconds to select all of the text, and then then another few seconds to copy it to the clipboard. So you'd have to figure out how to know when each step was done. On the old version of Foxit Reader I use (the last one that lets you choose the classic toolbar instead of that horrible Ribbon Mode), a progress window appears while selecting the text after pressing Ctrl-a. Then when that window disappears, you can go on to copy the text to the clipboard using Ctrl-c and another progress window appears while that takes place. By watching for these progress windows you could know when to take the next step. For a short document, the selecting and copying progress windows may appear only very briefly, but it seems that they are momentarily visible even then. I don't know if the same thing happens with the later versions of Foxit Reader. You'd have to test to see. Just another idea.

There are two updates available. The WinHTTP one shouldn't be ignored. Probably because you are running the 32 bit version of geckodriver. You can resolve by either -- switching to 64 bit version of geckodriver Add the "binary" option to your capabilities string (you should be able to find examples of this on the forum / wiki). P.S. Upgrading to the newest UDF release won't fix this issue, but it should give better error logging that helps with diagnosing issues such as this.

try to use: $_WD_DEBUG = $_WD_DEBUG_Full ConsoleWrite($_WD_HTTPRESPONSE & @CRLF) ConsoleWrite($_WD_SESSION_DETAILS & @CRLF) check this: #include "wd_core.au3" #include "wd_helper.au3" Global $sDesiredCapabilities, $sSession Global $sDriver = "C:\Users\Chris\Documents\Autoit_Programs\Firefox_Autoit_Webdriver\geckodriver.exe" ; <== Please modify this statement to your environment. ; Setup Firefox _WD_Option('Driver', $sDriver) _WD_Option('Port', 4444) $sDesiredCapabilities = '{"desiredCapabilities":{"javascriptEnabled":true,"nativeEvents":true,"acceptInsecureCerts":true}}' $_WD_DEBUG = $_WD_DEBUG_Full _WD_Startup() $sSession = _WD_CreateSession($sDesiredCapabilities) ConsoleWrite($_WD_HTTPRESPONSE & @CRLF) ConsoleWrite($_WD_SESSION_DETAILS & @CRLF) Exit show console output