Skip navigation
qSteve
qSteve
Currently Being Moderated

Can't see "Enforce strict scoping rules"

Jul 4, 2012 10:53 AM

I have a radio button group in which I'm attempting to deselect a button. There are examples by Niall and others that I've copied, but it's not working, apparently because this.initValue is not being passed from MouseDown to MouseUp. It seems that deselecting "Enforce strict scoping rules" might solve the problem, but this parameter is missing from the application.

 

I'm running ADEP Designer version 10, and there's nothing about scoping in either File Properties > Defaults or File Properties > Run-time. Anyone have any idea why it's not there?

 

Thanks, Steve

970 Views   8 Replies   Latest reply: Niall O\'Donovan, Jul 31, 2012 2:28 PM
 
Replies
  • Niall O\'Donovan
    Currently Being Moderated
    1. Niall O\'Donovan,
    Jul 4, 2012 11:35 AM   in reply to qSteve
    Report

    Hi Steve,

     

    That is strange, I can't see it either. It should be in the File > Form Properties > Defaults tab:

     

    Parallels Desktop1.png

     

    I am not sure what is going on, as it is still in the Spec. I will try and find out.

     

    In the meantime, here is another example for detecting key presses. I use it for deselecting a radio button some forms. We have an instruction for the user to hold down the Shift key while clicking: http://assure.ly/j1KdNq.

     

    I can't do more at this stage, but hope to come back to it.

     

    Thanks,

     

    Niall

     
    |
    Mark as:
  • qSteve
    Currently Being Moderated
    2. qSteve,
    Jul 4, 2012 11:49 AM   in reply to Niall O\'Donovan
    Report

    Thanks for the work-around, Niall. Works like a charm and is a LOT simpler! I'll still be interested in your findings re the missing function.

    Steve

     
    |
    Mark as:
  • Niall O\'Donovan
    Currently Being Moderated
    3. Niall O\'Donovan,
    Jul 4, 2012 3:41 PM   in reply to qSteve
    Report

    Hi Steve,

     

    It may be a week or two before we get any indication on this, but I will post if I hear anything.

     

    Also, looking at the XML Source in LC Designer ES3, it looks like the enforce strict scoping is turned on by default. However the UI does nto give any control over this. I am slow to recommend editing the XML Source, so hold off for the time being.

     

    Glad the other solution helped!

     

    Niall

     

     

    Also, see http://help.adobe.com/en_US/enterpriseplatform/10.0/DesignerScriptingB asics/WS92d06802c76abadb1c129a7d129f69171cd-7ff2.html.

     

    Message was edited by: Niall O\'Donovan

     
    |
    Mark as:
  • qSteve
    Currently Being Moderated
    4. qSteve,
    Jul 5, 2012 5:27 AM   in reply to Niall O\'Donovan
    Report

    Thanks Niall. What I'm not understanding is why your AssureDynamics form works for me when I open it in Designer and preview it but mine doesn't. The strict scoping parm in the XML is the same for both -- <?acrobat JavaScript strictScoping?> -- yet in your form, this.initValue takes the "1" on the mouseUp when the button is deselected, but on mine it's undefined. Could there be anything else causing this? Both forms are Dynamic XML and set to 9.1 or later.

    Steve

     
    |
    Mark as:
  • Niall O\'Donovan
    Currently Being Moderated
    5. Niall O\'Donovan,
    Jul 5, 2012 5:36 AM   in reply to qSteve
    Report

    Hi Steve,

     

    There probably is something else going on, but I'm not at my desk today, so can't check it out further at the moment.

     

    Maybe later,

     

    Niall

     
    |
    Mark as:
  • Niall O\'Donovan
    Currently Being Moderated
    6. Niall O\'Donovan,
    Jul 18, 2012 11:23 PM   in reply to qSteve
    Report

    Hi Steve,

     

    A couple of things.

     

    First in your version of the form, make sure that you have the corresponding script in the mouseDown even of the individual radio buttons:

     

    // Capture initial value of radio Button and save it as a member of the radio button object
this.initValue = this.rawValue;

     

    In relation to enforcing strict scoping in LC Designer ES3, the intention is to encourage best practice by automatically enabling strict scoping. This is a good thing!

     

    So if you open a new form in LC Designer ES3 (or you have a form where script scoping is selected/on), then the option to deselect/turn off strict scoping is NOT available in the File > Form Properties > Run-time panel:

     

    http://assure.ly/SJ5BWU (I can't include screenshots in the forum at the moment)

     

    This encourages the developer to follow best practice, by automatically enforcing strict scoping.

     

     

    On the other hand, if you have a form where the enforce strict scoping is (for what ever reason) turned off, then the option to enforce/turn on strict scoping is available in the File > Form Properties > Run-time panel:

     

    http://assure.ly/OIntMM

     

     

    I hope that clears that up,

     

    Niall

     
    |
    Mark as:
  • ashish gupta.
    Currently Being Moderated
    7. ashish gupta.,
    Jul 27, 2012 3:28 AM   in reply to Niall O\'Donovan
    Report

    Folks, this has also been updated in the Designer Scripting Basics guide here.

     
    |
    Mark as:
  • Niall O\'Donovan
    Currently Being Moderated
    8. Niall O\'Donovan,
    Jul 31, 2012 2:28 PM   in reply to ashish gupta.
    Report

    Thanks Ashish!

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points