Adjust the working pane zoom level to your particular liking.  Adjust the size of the lower pane (where properties are found).  Adjust your font / size as well as other available adjustments that affect how data is presented in the working pane.

I wish I knew what NW stood for.

kaak elbg

For me and all my colleague it is very annoying and also dangerous that In TIA the screen jums depending if i im above the middel then it jums to a nw up and under the middle the display jums to the nw below.

That happels:

-if i switch monitor on.

-if i switch monitor off

-if i download

Siemens do something at it !

When i close my FB and i open it it know exact where i am
Thus it is posible to do.

When you say to me i have too long networks why is it then posible to make it?

In FBD is always a lot bigger then in  other languages.

Please do sommething on this bigg problem 
I have asked so many times

And do also not say to me this is a Window mather becaus this is not!

Do you routinely work with NW collapsed, expanded, or mixture of both as needed?

If you minimize and then maximize portal's main window, does it alter the behavior in any way?

Definitely take a screen "video" showing the problem and submit to Siemens Support to see what can be done.

kaak elbg

NW  is Network:

I understand what you mean by the problem of networks "jumping" around on you.

However, Siemens is correct in that the "problem" is baked into how Windows O/S operates.  What you ask would require Siemens to create a "hack" or workaround for every window that they wish to NOT jump around.  Sure, they can use OOP to make it easier to implement, but that would add a lot of testing since it would start affecting every window (of which there are thousands).

I understand why they are choosing to ignore the request.

However, I think your assessment is correct.  If Siemens internal PLC programmers were forced to deal with this jumping behavior on a routine basis, they would likely walk over to the portal architects and ask for the very same behavior modification - or some alternate approach that prevents windows from causing networks to "jump".

Perhaps they should consider modifying the jumping behavior, like the speed at which it jumps could be slowed down so it is not so visually abrupt, or perhaps instead of allowing it to jump, they automatically pull the working pane out to a much taller floating pane (taller than the available screen height) which I *think* would not cause windows to "jump" at all.

Again, it would still feel abrupt with the window jumping out to a floating window, but if they added an "Options->Settings" checkbox to allow this or not (with the default to NOT), you could possibly get non-abrupt network visualization at the expense of dealing with re-docking floating working pane windows.

Does adjusting the zoom level improve the experience?

How about this as a currently available alternative:

Limit LAD/FBD blocks to a maximum of 6 networks.

Since the default working pane behavior is to show the first 6 networks, you would never need to expand a network - unless you previously collapsed them all.

That would mean a lot more FBs/FCs, which might not necessarily be a bad thing from a code reusability perspective.

kaak elbg

I have already many times give Siemens video's with this problem.

It is for Siemens also very easy to simulate!

The only answere i get that this is a Windows problem.
With this answere i do not agree.
When i close The FB  and close TIA  Then open TIA and open the FB

the view goes straight to the point in the network where I was when I closed the FB

I don't think anyone, except Royal Kaak, uses FBD

Otherwise this problem would have been solved long ago.

We are a big company and every programmer is annoyed by this problem