I’m a little confused, mostly because you’re talking about Adobe Reader which shouldn’t have a JavaScript Console. The Console is only available in Acrobat.

If you were actually talking about Acrobat, not Reader, then it’s probably a focus issue with the Console. I find in some cases it tries to remain on top of other windows and when the Acrobat window is closed (i.e. when you move away from the Preview tab in Designer), the Console may try to auto-hide itself. This behaviour often gets it into a state where it won’t show itself when you press “Ctrl + J”. To get it out of that state, I usually have to kill the Acrobat.exe process and then launch Acrobat again.

Somehow the ctrl+j shortcut didnt work for me either. I had to keep my adobe reader open to capture any javascript errors to show them at the console. Once i hit the error, i keep the console open and use it from there to show my console.println script.
i am using livecycle ES 8.2

You’re welcome!

When you preview your form in Designer or open it in Acrobat, you simply need to press “Ctrl + J” on your keyboard to see the JavaScript Console. If you’re using Reader, you won’t be able to see it since that feature isn’t available in Reader.

Thanks for the tip with
console.println(…);

YES the scripting and debugging features in designer are limited and need more attention if Adobe wants the platform to be a serious choice for big solutions/companies.

When you are used to code completion etc. from Visual studio, eclipse etc. you feel like you were set 5+ years back in time!

/Thomas
Jyske Bank – Denmark

It’s right in between app.alert and console.println – no RSI from closing the alerts, and no having to bring up the JavaScript console. But you do have to remember to remove this field (and the code that sets it) before you’re done with your form.