-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve transaction counter graph resolution and scale #487
Comments
Transaction counter has been updated to implement a more standardised graph using tkpath features with examples from SQL Server on Windows using GDI. The graph will redraw/resize as the window/canvas is resized: and adjust both height and width independently: The updated transaction counter will show 20 data points and move from right to left over time, with non-filled data points showing as 0 instead of building up the graph filling the entire chart with a smaller number of datapoints. The window can also continue to be dragged out to a standalone window. The default graph will be a polyline with a vertical colour gradient to white, however the previous ribbon effect will be possible as a non-default config option in the .xml config files only. The image shows an example of antialiasing from tkpath. This is in contrast to the current graph at v4.6 that does not use antialising. minor gradient effects have also been added to the CPU metrics Further testing and updates on Linux using Cairo Graphics prior to PR to fix the issue of the transaction counter graph not resizing when the window is resized. |
Linux example with MariaDB Trace shows use of cairo
Some minor further sizing adjustments are needed and further testing on Linux distros. |
The original transaction counter graph was something quick with no further dependencies, however expanding the window the graph size is fixed and doesn't scale as it could for example:
The graph should be updated to adapt when the window is expanded.
It will be possible to use the tkpath canvas already added here to give more advanced capabilities #478
The text was updated successfully, but these errors were encountered: