Page 1 of 1

Navigation through embedded module

Posted: Thu Jan 28, 2021 4:18 pm
by AdrianSan
Hi,

I have got the following problem: In the root panel of my project I have several embedded modules. One of them is intended to load a top menu, another one at the bottom loads a little alert table, etc.

I set a big module on the center to display the main thing. It displays a big area from which one is able to access different sub-areas, and diferent sub-areas subsequently.
The problems is, when I access a certain area whose panel is (for example) 400x400, and then I go to a bigger one, it doesn't display the whole picture, but only the first 400x400 part of the panel, and the rest remains empty.

Do I need to have all the panels with the same size? Or is there a better solution?

Thank you in advance.

Re: Navigation through embedded module

Posted: Fri Jan 29, 2021 9:01 am
by leoknipp
Normally a root panel uses the full size of the module where it is loaded to.
An embedded module does not resize automatically to the size of the loaded panel.
Possibly the problem in your case it that the module has a size of 400x400 pixels and therefore you do not see the complete panel loaded to the module.

It is always of interest which WinCC OA version + patch level and which operating system is used.

Best Regards
Leopold Knipp
Senior Support Specialist

Re: Navigation through embedded module

Posted: Fri Jan 29, 2021 11:41 am
by AdrianSan
Thank you for your response,

I am using 3.16 P021.

My embedded module shape is 1500x600.

In the initialization, I load in that module the panel A_PANEL which is also 1500x600, then I click certain button to load the B_PANEL which is 600x600. When I load again the A_PANEL, it appears cut in the size of the B_PANEL.

To add some information, A_PANEL and B_PANEL have different panel backgound colors, and when I return to A_PANEL, althouth it is cut, the backgound color is correct.

Re: Navigation through embedded module

Posted: Mon Feb 01, 2021 3:38 pm
by AdrianSan
Hi again,

I have discovered that this problem only happens when you write the panel path along with its extension in the function RootPanelOnModule.

Problem solved for me. Thank you.