Skip to content

Plot and filter values are saved with the project but not displayed when loading project #1222

Closed

Description

@mgrojo

Details for the issue

The plot data and current filter is correctly saved in the project. But when the project is reopened and the information restored, the filter values in the header are not displayed. The appearance is that of an unfiltered table, but it is actually filtered internally. The plot is neither recovered, but the data internally is present.

Pressing the refreshed button solves both issues. The plot is drawn, and the filter values are visible again in the header.

It's a minor issue, but something that we should take a look at some moment.

Useful extra information

I'm opening this issue because:

  • DB4S is crashing
  • DB4S has a bug
  • DB4S needs a feature
  • DB4S has another problem

I'm using DB4S on:

  • Windows: ( version: ___ )
  • Linux: ( distro: Ubuntu 16.04.3 )
  • Mac OS: ( version: ___ )
  • Other: ___

I'm using DB4S version:

  • 3.10.1
  • 3.10.0
  • 3.9.1
  • Other: git commit a03a901 and previous ones

I have also:

Activity

  1. added
    bugConfirmed bugs or reports that are very likely to be bugs.
    on Nov 9, 2017
  2. justinclift commented on Nov 9, 2017

    @justinclift
    Member

    Good discovery. 😄

  3. mgrojo commented on Dec 11, 2017

    @mgrojo
    MemberAuthor

    Moreover, if in this situation (table filtered and restored though project file, but filter is not visible in the header) I click on "Duplicate record" or press tab at the last cell, the application crashes.

    Clicking Refresh after opening the project always fixes everything, the filter is visible and there are no subsequent crashes.

  4. mgrojo commented on Jan 8, 2018

    @mgrojo
    MemberAuthor

    Now I only reproduce the filter issue. I cannot reproduce the crash nor the problem with the plot. But trying to crash it I stumbled upon #1289 😄

  5. mgrojo commented on Oct 15, 2018

    @mgrojo
    MemberAuthor

    I'll close this issue, since it covered some problems, some already fixed, and the remaining one is better described in #1573.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugConfirmed bugs or reports that are very likely to be bugs.crash

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions