Validating Data in ScriptUI

@Peter Kahrel - I ran into a new issue, and I hope I'm missing something obvious, but I'm somewhat afraid I'm not.

Now that the code is pretty much working, I decided I might try making the window borderless.

I looked at Pages 8 and 9 of the guide.

I can make the window borderless, but I agree, it looks plain with no border on it.

I tried:

w = new Window ("dialog", undefined, undefined, {borderless: true});
w.margins = [0,0,0,0];
myPanel = w.add ("panel");
myPanel.add ("statictext", undefined, "borderless: not quite true");
w.show ();

And it looks like Peter's example. There is a THIN gray border around the window, but not really noticeable compared to no border at all. (It also locks up FrameMaker and when I click the blue square, it says FM did not respond and I have to close and re-open it manually).

I tried:

w = new Window ("dialog", undefined, undefined, {borderless: true});
w.margins = [0,0,0,0];
myPanel = w.add ("panel", undefined,"",{borderStyle:'black'});
myPanel.add ("statictext", undefined, "borderless: not quite true");
w.show ();

And that gives me more what I am looking for (and also locks up FM).

However, I have a bounded window since I wanted my panels side-by-side, so my window looks like this:

var win = new Window("palette", "Update Document Variables:", [$.screens[0].right/2 - 255,$.screens[0].bottom/2 - 143, $.screens[0].right/2 + 255, $.screens[0].bottom/2 + 143],{borderless:true}); // bounds = [left, top, right, bottom] Width - 505 Height 285
    win.margins = [0,0,0,0];
//    myPanel = win.add ("panel", undefined,"",{borderStyle:'black'});    
    myPanel = win.add ("panel",[0,0,200,200],"",{borderStyle:'black'});
    win.radioPanel = win.add("panel", [5, 5, 230, 250], "");
    win.Panel2 = win.add("panel", [235, 5, 505, 250], "");
    win.okBtn = win.add("button", [187,255,277,280], "OK"); //Centered on divider
	win.okBtn.Active="True"
    win.defaultElement=win.okBtn;
	win.okBtn.onClick = function() {
	    win.close();
     }    
    win.show();

The commented line didn't seem to do anything. The new bounded panel looks like what I want, but it is covering over my other panels and controls.

Is there a way to make the new panel transparent?

If not, I think I can get the effect I want by:

• Changing the panel name to P3.
• Expanding the bounds of P3 to match the window dimensions.
• Moving all my controls to be on top of P3 by doing a find and replace on "win." and carefully replacing with "win.P3." (So win.Panel2 becomes win.P3.Panel2.), while being careful to NOT change lines like win.Close(); and win.Show(); to win.P3.Close();

Is there an easier solution?

Ran into another snag. I'll try to be brief.

I have a pop-up palette window with radio buttons on the left and input boxes and an apply button on the right. You click a radio button and the script reads values into the input boxes and you click Apply and it writes the input box values to variables. That works fine.

I wanted to add a "MouseOver" function so that if the apply button was enable, but was not clicked, you would get a confirmation dialog to drop the changes BEFORE the button click was applied.

The "click" code looks like this:

win.radioPanel.rad01.onClick = win.radioPanel.rad02.onClick = win.radioPanel.rad03.onClick = function () {

		if(win.radioPanel.rad01.value) { 
// Do stuff;
}
}

I tried to add something similar for the first button:

      win.radioPanel.rad01.onMouseover = function(){
          if (win.radioPanel.rad01.value){
            alert("mousedover!");
            }
}

But it doesn't seem to be doing anything - I never get the alert - unless I made a typo.

I tried onmouseover and onMouseOver and without the if statement and no luck - but no real error messages either.

@Marc Autret - That works amazingly - exactly what I was asking for. I don't really understand it, but I can make it work. Thank you SO much!!!

Playing with text then textselection, in that order, may solve the cursor issue in EditText widgets. That's a bit of black magic so I do not guarantee the universality of the following code:

Works fine on my system - as long as it works on Windows in FM15 and up, I'm fine. (Actually, as long as it allows input on those systems, I'm okay with it. (And ESTK seems a bit too good at ignoring errors - i.e. many times my code runs (improperly), if I just didn't define something properly. VBA would have thrown an error - but that has plusses also.

Note 2. — To my knowledge, the property EditText.graphics.backgroundColor is no longer effective in CC (?) but it may depend on the OS (?) [Still works in CS3-CS6 though.]

 Pity - it is working for me and I really like the effect.  I assume CC is Creative Cloud and CS is Creative Suite.  How can I know what I am running. It is working for me in Win10 and I see from time to time that Creative Cloud has been updated, so either I have CC but am using something else, or it is working again.

= is used to assign a value to a variable.

== and === test equality. === is used for strict equality, which means that the two items you compare must be the same type. == is for looser comparisons. == is slower because it tries to coerce the two items into type-equality.

Example:

var a = 5;

var b = '5';

a == b; // => true

a === b // => false

a is a number, b is a string. Strict comparison returns false because the variables are not the same type. Loose comparison returns true, it successfully coerces the variables into the same type (string or number, I don't know which).

Because strict comparison evaluates considerably quicker you should use it where you can. Especially in InDesign's DOM, when you test some enumeration repeatedly. For example

if (myPage.side === PageSideOptions.LEFT_HAND) {

is considerably quicker than

if (myPage.side == PageSideOptions.LEFT_HAND) {

If you don't know whether the two items to be compared are type-compatible, use ==