Inconsistent docked and independent DBMS Output window functionality. (4274472)

When the DBMS Output is docked in the Editor and the independent DBMS Output window (from View | DBMS Output) is selected,  each run their own dbms_output.get_line to retrieve the buffer when polling is turned on. Inconsistent window output is seen.

WORKAROUND:  
None

STATUS:
Waiting for fix in a future version of Toad for Oracle.

An example:

Execute the following statement in the Editor with F9:
exec DBMS_OUTPUT.put_line ('Debugger Test');

Noticed that the DBMS Output docked in the Editor and the independent DBMS Output window (from View | DBMS Output) each run their own dbms_output.get_line to retrieve the buffer when polling is turned on. However, turning off the polling from the docked window in the Editor also turns off the polling from the independent window. SQL Monitor shows two dbms_output.disable commands are sent to the database. The green light remains on in the independent window, misleading the user that polling is still on. It looks like a bug where the Toad programmer didn't turn off the green light, or they weren't suppose to send two dbms_output.disable commands.

Following this, clicking on the green light in the independent window, it will remain green and send an

dbms_output.enable. Clicking on it again it will turn red, and send a correct dbms_output.disable.

The polling is on in the independent window and off in the docked window, running the statement above will turn on polling in the docked window.