Non-Maximized Window changes location

This could be my own problem, but with as much time as I’ve spent attempting to correct it, it sure seems like a glitch in java or Ignition. I have a window with a report in it. All the behavior properties are set to false (closable, maximizable, resizable, start maximized). Originally I wanted the window centered in the client but NOT maximized so I had a script on the window to center it upon activation (event = internalFrameActivated). When the client opens for the first time, the window appears exactly as I want it. There are two docked windows that contain navigation tabs at the top and bottom of the screen and there is plenty of space between the report window and the two docked windows when I open the client at first. When I navigate to another tab and then back to the original window, it will automatically maximize, unlike when the client is first opened.

I think I’ve been through every possible combination of docking/floating and behavior properties. The window will not stay where it is when the client first opens if I navigate away and then back to it. If I choose to dock the report window north or south, navigate away from it, and come back, the window will not maximize but it will change to the opposite docking location.

Ideally, the window will be centered and not maximized. I could live with docking it north or south as long as it doesn’t change. Has anyone experienced this issue?

The most likely problem is that you are using the system.nav.swapTo() function (the Tab Strip component uses this) instead of the system.nav.openWindow() function. What’s special about the swapTo() function is that it opens the window you specify in the same size and location as the current ‘main window’ of the client. The ‘main window’ being the one that is open, maximized, and not docked.