In ADS v20.0 when a query has multiple errors the Messages tab will show at the bottom of the QA but all you see is a window that says Selected Cell Content. We have found that the actual messages are in a window behind the Selected Cell Content window. This is confusing to users as they have no idea what the Selected Cell Content window is for, and there is no documentation explaining its use (at least none that I or the user could find).
The Selected Cell Content. window only appears if there two errors or more. What we'd like to see is; 1) The window does not cover the messages window went it first appears; 2) There is some documentation covering this window's function.
51 KB
109 KB
151 KB
17 KB
License Key: 3A4754503E9C6EE1CF96CB63473781EEF292D4B07776DC81****************
Product: Aqua Data Studio
Version: 20.0.0
Build #: 56860
Build Date: 2019-May-10 12:12:58 PM
Operating Environment: Windows 10 (10.0, amd64) / Cp1252 / en / US / Oracle Corporation 1.8.0_172-b11
Memory: Max=3,817,865,216; Total=498,073,600; Free=303,305,496; CPUs=8
In-Window Graphics Capabilities
Graphics Vendor: ATI Technologies Inc.
OpenGL Renderer: AMD Radeon R5 430
OpenGL Version: 4.5.13544 Compatibility Profile Context 25.20.15011.1004
Double-Buffering: Enabled
Anti-Aliasing: Enabled
Anti-Aliasing Sample Count: 8
Hardware Acceleration: Enabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 0 Green: 0 Blue: 0
Initialization Time: 1055 ms
Offscreen Graphics Capabilities
Graphics Vendor: Brian Paul
OpenGL Renderer: Mesa OffScreen
OpenGL Version: 2.1 Mesa 7.8.2
Double-Buffering: Disabled
Anti-Aliasing: Disabled
Anti-Aliasing Sample Count: 0
Hardware Acceleration: Disabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 16 Green: 16 Blue: 16
Initialization Time: 45 ms
Hardware PBuffer Available: No
Using PBuffer: No
Using Ram Buffer: Yes
Offscreen Rendering: Enabled
Offscreen Buffer Size: 800x600
I am able to recreate what the customer is seeing using a SQL Server 2016 machine. When executing multiple statements that error, a multiple error results screen is opened. Below that screen is a cell content screen which lets you display the contents of the cell that is selected in the multiple error results screen. Typically, the screen's divider is set to almost equally split the results screen. If the selected cell content screen should get expanded up where it covers the multiple error results screen and the user reruns the queries and closes ADS, the screen will always remain in that position when getting multiple errors next time you open ADS and execute multiple error queries.
The reason this is happening is that the properties querywindow.message.results.divider is getting set to 0 when ADS gets closed since the divider is now at zero because the selected cell content screen completely covers the results screen. See ResultSetTableView class at line 33 and QueryTableSettings class.
The only real way to reset the divider now is to set the divider where you want it and rerun the queries that fail. Once you exit ADS, the querywindow.message.results.divider will get reset.
One suggestion is to change the code so that if querywindow.message.results.divider is set to zero at query execution time, to reset it to the default value. Another option is to set querywindow.message.results.divider when the divider is dragged up or down. The former being the preferred method.
Check with Asif on this as he is more knowledgeable.
Thanks,
Tom
I am able to recreate what the customer is seeing using a SQL Server 2016 machine. When executing multiple statements that error, a multiple error results screen is opened. Below that screen is a cell content screen which lets you display the contents of the cell that is selected in the multiple error results screen. Typically, the screen's divider is set to almost equally split the results screen. If the selected cell content screen should get expanded up where it covers the multiple error results screen and the user reruns the queries and closes ADS, the screen will always remain in that position when getting multiple errors next time you open ADS and execute multiple error queries.
The reason this is happening is that the properties querywindow.message.results.divider is getting set to 0 when ADS gets closed since the divider is now at zero because the selected cell content screen completely covers the results screen. See ResultSetTableView class at line 33 and QueryTableSettings class.
The only real way to reset the divider now is to set the divider where you want it and rerun the queries that fail. Once you exit ADS, the querywindow.message.results.divider will get reset.
One suggestion is to change the code so that if querywindow.message.results.divider is set to zero at query execution time, to reset it to the default value. Another option is to set querywindow.message.results.divider when the divider is dragged up or down. The former being the preferred method.
Check with Asif on this as he is more knowledgeable.
Thanks,
Tom
Hi Shrey, Asif,
Not sure that this is the right approach. I thought that you were going to check the divider location and if it was set to zero or a low value, set it divided equally. Also, the original code set this in a thread. Not sure why but maybe you should also.
Asif, Thoughts on this?
Thanks,
Tom
Hi Shrey, Asif,
Not sure that this is the right approach. I thought that you were going to check the divider location and if it was set to zero or a low value, set it divided equally. Also, the original code set this in a thread. Not sure why but maybe you should also.
Asif, Thoughts on this?
Thanks,
Tom
@Dev,
We are good with the current solution. I had a call with Tom regarding the same. The current fix to reset the vertical splitter for each execution is simple and reasonable in terms of what customer wants.
Thanks
Asif
@Dev,
We are good with the current solution. I had a call with Tom regarding the same. The current fix to reset the vertical splitter for each execution is simple and reasonable in terms of what customer wants.
Thanks
Asif
Revision #58492
Committed by shrey.pasari
Changes look OK.
Revision #58492
Committed by shrey.pasari
Changes look OK.
QA verified: Selected cell content window appeared if errors triggered count 4 or more.
QA verified: Selected cell content window appeared if errors triggered count 4 or more.
assigning to automation team for further action on this
assigning to automation team for further action on this
Automation is not applicable for this ticket. Since manual QA verification was done, moving this to verified state.
Automation is not applicable for this ticket. Since manual QA verification was done, moving this to verified state.
Issue #15724 |
Verified |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 6 |
No time estimate |
License Key: 3A4754503E9C6EE1CF96CB63473781EEF292D4B07776DC81****************
Product: Aqua Data Studio
Version: 20.0.0
Build #: 56860
Build Date: 2019-May-10 12:12:58 PM
Operating Environment: Windows 10 (10.0, amd64) / Cp1252 / en / US / Oracle Corporation 1.8.0_172-b11
Memory: Max=3,817,865,216; Total=498,073,600; Free=303,305,496; CPUs=8
In-Window Graphics Capabilities
Graphics Vendor: ATI Technologies Inc.
OpenGL Renderer: AMD Radeon R5 430
OpenGL Version: 4.5.13544 Compatibility Profile Context 25.20.15011.1004
Double-Buffering: Enabled
Anti-Aliasing: Enabled
Anti-Aliasing Sample Count: 8
Hardware Acceleration: Enabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 0 Green: 0 Blue: 0
Initialization Time: 1055 ms
Offscreen Graphics Capabilities
Graphics Vendor: Brian Paul
OpenGL Renderer: Mesa OffScreen
OpenGL Version: 2.1 Mesa 7.8.2
Double-Buffering: Disabled
Anti-Aliasing: Disabled
Anti-Aliasing Sample Count: 0
Hardware Acceleration: Disabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 16 Green: 16 Blue: 16
Initialization Time: 45 ms
Hardware PBuffer Available: No
Using PBuffer: No
Using Ram Buffer: Yes
Offscreen Rendering: Enabled
Offscreen Buffer Size: 800x600