I am currently developing a panel running on InDesign CS5, CS5.5 and CS6. For some internal specific reason, the panel (of type csxs:CSXSWindowedApplication) has its visible property set to false; in its "Lifecycle", the autovisible is unselected and the panel starts on event "applicationActivate".
This way the panel works as I am expecting, at least on CS5 and CS5.5; unfortunately this is not happening under InDesign CS6. The best way to explain what I am obtaining (expected or not) is by running a ExtensionBuilder 2.0 existing demo project. The example I am talking about is the "CSXSWindowedAppDemo" project. After having imported it, the visible property of the CSXSWindowedApplication must be added and set to false on the "main.mxml" file.
Then, some adjustment must be done by ctrl-clicking the project and selecting the "CS Extension Builder > Bundle Manifest Editor" menu. First of all, the "Max. Target Version" on the Bundle tab panel must be set to "empty" (to be sure the panel could be run on CS5.5 and CS6); then, after having clicked on the "Extension" tab panel, the "AutoVisible" property must be unchecked and the "applicationActivate" event must be added to the "Start on event(s)" list.
If the panel is executed on CS5 and CS5.5 the behaviour is the expected one and could be reproduced this way:
As expected, the panel should open by presenting the "Status Bar" tab panel.
Now on InDesign CS6:
Action #4 doesn't open the panel, nothing happens and re-opening it by clicking on its menu again will cause the panel to be "re-executed" from the scratch by presenting the first tab panel again (as it was executed the first time). Then, the other steps:
Now, the panel is shown as expected and the "Status Bar" tab panel is shown.
I tried to figured out a solution for this, but I don't actually understand what's happening on CS6.
Any help would be really appreciated.
I am also facing the exact issue.
My extension is not working for CS6 in windows. But It is working for CS5, CC version on windows and Mac both.
Is there any work around to this problem?
Please help me on this, its urgent..
I am surprised to know that you are not facing against this behaviour on CC too (because I had on CC as well); when I asked to the Adobe Developer Support I was told to create a separate project for CS6 and CC and effectively this solved the issue. Unfortunately this way, I had to manage two different projects instead of one.
Hope this could help
Sorry for late response.
Thanks it worked.