Problem deleting data in first fit page (Trac #929)

[sasview-bot]

If send data to FitPage1 and then try to delete it, the FitPage1 deletes and "points" to FitPage2. As soon as you send other data to Fitting, the following error appears:

Fitting set_data: in method 'AuiNotebook_GetPageIndex', expected argument 2 of type 'wxWindow *'

Migrated from http://trac.sasview.org/ticket/929

{
    "status": "closed",
    "changetime": "2017-05-30T03:10:18",
    "_ts": "2017-05-30 03:10:18.137967+00:00",
    "description": "If send data to FitPage1 and then try to delete it, the FitPage1 deletes and \"points\" to FitPage2. As soon as you send other data to Fitting, the following error appears:\n\n{{{Fitting set_data: in method 'AuiNotebook_GetPageIndex', expected argument 2 of type 'wxWindow *'}}}",
    "reporter": "Adamo",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView Bug Fixing",
    "time": "2017-04-06T16:07:53",
    "component": "SasView",
    "summary": "Problem deleting data in first fit page",
    "priority": "major",
    "keywords": "",
    "milestone": "SasView 4.1.1",
    "owner": "krzywon",
    "type": "defect"
}

[smk78]

Trac update at 2017/04/06 16:38:30: smk78 commented:

This issue does not exist in 4.0.1 or 3.1.2

[sasview-bot]

Trac update at 2017/04/06 17:14:37:

• krzywon commented:

I'm the last one to change the fitting perspective. I must have broken it so I'll try to fix it.

• krzywon changed owner from "" to "krzywon"
• krzywon changed status from "new" to "assigned"

[sasview-bot]

Trac update at 2017/04/07 08:08:14: krzywon commented:

In changeset dab94f6:

#!CommitTicketReference repository="sasview" revision="dab94f667c2e72b4596de4958804211083ca97a9"
Deleting data from first fit page is no longer causing the issue. see #1011

[butlerpd]

Trac update at 2017/04/08 15:31:00: butler changed milestone from "SasView 4.2.0" to "Milestone 4.1.1"

[butlerpd]

Trac update at 2017/05/30 03:10:18:

• butler commented:

Testing release candidate 4.1.1 installable for windows from official Jenkins server shows that this problem is now fixed. Closing this ticket in preparation for a final release.

• butler changed resolution from "" to "fixed"
• butler changed status from "assigned" to "closed"