Script Window Open but not Viewable

[#1]

Hello,

I am encountering a weird bug in which I can open a script file, but am unable to view it. It looks

I click on the windows drop down viewer and don't see it. I open the Window Task Bar and click to select the script file, but nothing happens.  I can open the script in a different instance of JMP as well as other scripts and tables in this instance of JMP...

Please advise!

Sincerely,

Matt Goodlaw

[#2]

A couple of things might be happening.  There is a Preferences setting and also a code sequence within a script that will force it to run, without opening up.  To bypass this, try holding down the Control Key (CNTL) when you click on the file to open it.  That should override the run only option.

[#3]

hmm, I reset my preferences back to default, still no luck.  I tried the holding down of (Ctrl), no luck.I can click on the script window but it doesn't open

Here is what I see:

[#4]

I assume the file is saved on disk.  Have you tried holding the CNTL key down when opening the file from disk.

If necessary, try renaming the file extension to "txt" and then opening it with Notepad.  This is very curious.

[#5]

Still no luck. I openned the file holding Ctrl down and no luck.  What's crazy is that .jsl file opens perfectly and runs in JMP 13, just not JMP 13 Pro.  It had been working fine in the Pro version up until a couple of hours ago.

[#6]

Time to reboot, then if it still is having an issue, rename the extension to "txt" open it, and then cut and paste it into a new JSL entry.  That is at least what I would try.  Oh.....and send an email to the JMP Support folks

     support@jmp.com

[#7 · Accepted solution]

I wonder if the window is off-screen.  JMP saves the position/size of each document.  If you see the window in the taskbar, can you right-click and select "Move" to reposition the window?

[#8]

That was it.. I am in a new office and yesterday, I third monitor on the wall was connected and I guess they tested it with that script window.  The monitor was off when I returned and ... Thanks txnelson for the initial suggestions.