Changes to main connection propagated to multiple windows...?

[null0000]

I am not sure if it a bug or a feature (intended behavior):
I had several windows being opened.
There were different types:
P - program window [1]
S - SQL window [2]
S - SQL window [3]
C - command window [4]
S - SQL window [5]
C - command window [6]
windows 1,3,6 from above were opened for the same connection -- Main Connection.
However , when Main Connection was changed that change propagated to all those windows (1,3,6). Frankly , that not what i expected -- IMHO regardless how window was opened , there is indicator on status line, so why would change to Main Connection should propagate to all those windows? If a window to be pointed to other connection then it can be changed "locally" and explicitly !
if it is a bug , can please address it?
if it is a feature, can please make it configurable? (that any changes to Main Connection won't inherently effect other screens)

 

[Maxmix]

From documentation:

17.2 Window connections
...
Window connections can either be pinned or unpinned. When unpinned ( ), the window connection
will follow the main connection when the main connection is changed. When pinned ( ), the window
connection will remain the same when the main connection is changed. To view or change the pinning
of the window connection, view or click on the button in the connection status panel.
Newly created windows can either be pinned or unpinned by default, depending on the corresponding
preference (see chapter 20.1). If you explicitly change an unpinned window connection, it will
subsequently be pinned.

HTH

 

[null0000]

Thanks!! Chapter 20.1 was right on the target!