That's really weird. Predictably, works fine here.
So, I've narrowed it down to this: If I open the project from the startup window I get this
You can see that the panel has no window frame around it. It can't be dragged, resized or closed. If on the other hand I open the project through the menu File > Open Project or File > Open Recent and after I select the panel from the extensions menu It shows up correctly.
I hope this helps
Windows 7, eh? Same results of you turn Aero off?
2. I'll ask the CEP team.
Turns out, that might be the result of the panel returning some strange error code during initial display. The only other time we've seen that behavior are when 1) upon first launch, the panel returns an error, or 2) there's no valid Workspace available. Since your screenshot shows a Workspace, we can eliminate option 2)...
Confirmed; you're using this sample panel, unmodified?
I have a 9.1 update to PProPanel, which I'll push soon.
Any luck on setting breakpoints (in Chrome Dev Tools) in PProPanel's OnLoaded(), to see what's going on? For debugging instructions see Samples/ReadMe.md at master · bbb999/Samples · GitHub, and Davide Barranca also has a good post on the subject: HTML Panels Tips: #1 Debugging | Photoshop, etc.
Don't let me push you to upgrade to upgrade before you were going to, but I'd be curious to see whether you can still reproduce the behavior in the just-released 9.1.
I am using the unmodified sample, yes. And I have upgraded to 9.1 but the issue is still there.
As for debugging in Chrome tools I think there is an issue. I am using the debugging technique in your links already, but the localhost:7777 is unavailable until after the panel has been opened. When it is open, I can click the link and put breakpoints etc but the onLoaded() is already long called. Any other way to see what's going on in that method? How about the ESTK? I haven't quite figured out how to use that one though. If there are any nice blog posts about it like the one you just showed me let me know.
You're right about it being tough to debug a panel's entry point function (debugging not available until it's open). Yes, you can definitely debug in ESTK!
+ Open /PProPanel/jsx/Premiere.jsx, in ESTK.
+ Set breakpoints everywhere you want.
+ Select PPro CC 2015 as the target app, but DON'T click the 'chain link' button to connect.
+ Launch PPro; if PProPanel is open, close it.
+ From within ESTK, click the 'chain link' button to connect.
+ Open PPro, use buttons; you should hit breakpoints in ESTK.
It's not in the official depot yet, but here's my updated PProPanel; it should supersede the panel you already have, and I'm curious whether you'll see the same behavior.
It worked like a charm! What did you change if I may ask? What was the error being thrown?
I did not dwell too much on the ESTK as my immediate problem is now solved. BTW, those very specific steps that you described there are not in the readme.md on github. It'd be nice if you made those public as well.
I'm not sure which change, helped; I changed all kinds of stuff, between the last push to the public depot and this one.
Good request; I'm getting planning out an 'on-boarding' panel development video, and [above] would fit in nicely.