Why does debugger menu entry not exist in Acrobat 7.1.0

Question

Today I decided to start using the JavaScript functionality of my Acrobat 7.1.0 (updated a few days ago from 7.0.x). First I searched for some documentation and found the original "Acrobat JavaScript Scripting Guide" for Acrobat 7.0, document release date July 19, 2005. What made me doubt about the quality of my environment is that there are always some features mentioned that do not at all exist in my Acrobat, such as menu entries like "Debugger" under "Advanced - Javascript". The only thing I find there is "define document actions" (menu entry translated from German). Reading other posts in this forum concerning Javascript I searched other places like acrobatusers.com and, checking the tutorials, I saw screenshots of preference screens containing more items than my ones, especially more items in the "debugger" panel of the "Javascript" entry. When searching places on my drive where Acrobat should expect JavaScript files like "Program Files\Adobe\Acrobat 7.0\Acrobat\Javascripts" I remember having read that there should be more files than just "Websearch.js" and "JSByteCodeWin.bin" (as it is in my case; but I'm not sure what actually should be there further).
So far the only thing I can do to open the console is defining some action related with files (but only unhandy ones like "when closed" or "when saved"). The only way I know to open the JS debugger is defining invalid JS code for some file action and perform this action, then the debugger shows up along with the console, complaining.
Strolling arround in my Acrobat program subdirectories I found documentation and a runnable named "ExtendedScript Toolkit" that seemed to work well (though I could not try it out seriously as it obviously is quite complicated because it relies on the InDesign object model). Did ExtendedScripting coming along with InDesign spoil my normal JavaScript environment in Acrobat? Or was it the update from Acrobat 7.0.0 to 7.1.0? How can it be that menu entries everybody else is talking about are not at all visible in my installation though I desparately enabled almost everything in my Acrobat preference settings? Are there some paranoid web security defaults making entries disappear in my installation?
Any suggestions will be greatly appreciated!
Richard

Answer 1

Bernd,
the matrix is for Acrobat 9 only and thus not totally liable. However, as for V9 the topic of scripting or debugging is not even touched in the whole matrix, one might suggest that V7 would also make no differences in that area.
I am only guessing, but the fact that I do not find any hint about a problem similar to my one might have to do something with the "ExtendedScript Toolkit" I mentioned above. If the behavior of my Acrobat installation had been changed due to installing ExtendedScript, this would be a kind of (intended) bug most users would not complain about, because: ExtendedScript comes along with software like InDesign, and the typical ID user is not the one developing JavaScript under Acrobat.
Searching Google for ExtendedScript I found the Adobe download area and clicking on the item it says:
The ExtendScript Toolkit (ESTK) 1.0.3 is a scripting utility included with Adobe® Creative Suite 2 and other Adobe applications. The ESTK is used for creating, editing, and debugging JavaScript to be used for scripting Adobe applications.
Looking up documentation on ExtendedScript (which was not very easy to find) I noticed some examples about adding a document to the target application by executing the line:
app.document.add();
As I am starting the ES toolkit as an own main program, I am getting the error message that this call is not executable for the target application "main", which I can accept. Maybe there is a way connecting Acrobat to ExtendedScript, maybe there is even a way to reanimate "normal" scripting, maybe normal scripting is not even unconscious but only sleeping and can be woken up easily ...
Maybe the best way to find out is searching for a forum about scripting (albeit extended or normal). Funny, though, that my Acrobat does not at all match the original scripting documentation of Adobe concerning such elementary things like menu entries being present (especially see second attachment: "Erweitert" translates to "Advanced", "Dokument-Aktionen festlegen" to "Define document actions". Where is the "Debugger" entry???).
If I believe others here in this forum saying that the "Debugger" entry normally is appearing in the Javascript menu. Obviously the Acrobat software contains program code to hide or remove this entry permanently. Furthermore, somebody else, also a member of the Adobe stuff, has written the documentation that does not at all contain any applying description of conditions about hiding the menu entry. What I would appreciate is if Adobe would make those two persons talk to each other about what they are doing. By that, other people like me could save a lot of time.