Skip to content
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

Unable to select points on very large Stacked Dots plot #5119

Closed
IanMayo opened this issue Jun 18, 2021 · 3 comments · Fixed by #5139 · May be fixed by #5142
Closed

Unable to select points on very large Stacked Dots plot #5119

IanMayo opened this issue Jun 18, 2021 · 3 comments · Fixed by #5139 · May be fixed by #5142
Assignees

Comments

@IanMayo
Copy link
Member

IanMayo commented Jun 18, 2021

When doing single-sided reconstruction, analysts are trying to minimise the errors on the Stacked Dots plot.

While doing this, they may select some data points to delete, if the errors are really large.

Analysts have found it's not possible to select data-points on the far-right of the plot.

Note the unusual workbench layout in the following animation. The users use huge monitors, this layout is a way of reproducing the width of the plot.

screencast

More detailed video.

The issue only arises when then the graph is really, really wide, something like 2000 pixels wide.

That makes me think the code to convert from screen to data coords isn't quite right - and some scaling factor is wrong.

The issue may be in BaseStackedDotsView.chartMouseClicked() - possibly in the logic for findSelectedPlot.

@IanMayo
Copy link
Member Author

IanMayo commented Oct 12, 2021

Updated version delivered.

When I click on the Absolute or Error portion of the Bearing Residuals Plot nothing happens,
but, a message appears in the Properties Box “The Active Part does not supply properties”

Requires further investigation.

Update an onsite investigation was conducted in Nov/21. The issue only occurred on PCs with NVidia graphics cards. The issue didn't occur on PCs with the Intel UHD Graphics driver.

@IanMayo
Copy link
Member Author

IanMayo commented Jan 7, 2022

Note: it may be worth running Debrief with graphics acceleration switched off, just in case, as detailed here:
https://www.jfree.org/forum/viewtopic.php?t=22676#p78405

@IanMayo
Copy link
Member Author

IanMayo commented Mar 9, 2022

Ok. Onsite computing support were able to resolve this. The just renamed .eclipse and .debrief preferences folders, and re-opened Debrief. Debrief created new (empty) settings folders, and the problem was resolved.

This doesn't explain why the only people with the problem were those with NVidia graphics cards, but maybe:

  • the PCs were built around the same time, and suffered from a Debrief issue present around then
  • the issue is related to those graphics cards
  • the issue is because the PC was first used with one graphics card, then changed to the new one, leaving some inconsistency in settings.

@IanMayo IanMayo closed this as completed Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants