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

[FIX] OWTable: Don't set selection when there is no data on input #3693

Merged
merged 1 commit into from
Apr 1, 2019

Conversation

rokgomiscek
Copy link
Contributor

Issue

Fixes #3451.

Description of changes

Fixes the bug by adding an additional check.

Includes
  • Code changes
  • Tests
  • Documentation

@codecov
Copy link

codecov bot commented Mar 22, 2019

Codecov Report

Merging #3693 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3693      +/-   ##
==========================================
- Coverage   84.52%   84.51%   -0.01%     
==========================================
  Files         373      373              
  Lines       68391    68393       +2     
==========================================
  Hits        57805    57805              
- Misses      10586    10588       +2

@janezd
Copy link
Contributor

janezd commented Mar 26, 2019

This fixes the symptom, but the real problem is that selection is non-empty although there is no data. Such state is invalid and may cause other problems elsewhere in the widget. Could you investigate why this happens and how to prevent it?

@rokgomiscek
Copy link
Contributor Author

I think this now fixes the problem. The old selection was stored in __pending_selected_rows and __pending_selected_cols, which were used to restore selected_rows and selected_cols respectively. My previous fix didn't empty the selections, only didn't pass it forward.

@janezd janezd merged commit 179abe2 into biolab:master Apr 1, 2019
@rokgomiscek rokgomiscek deleted the owtable-fix branch April 5, 2019 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants