Opened 2 years ago

Closed 21 months ago

#645 closed defect (fixed)

GUI logic problem in Batch vs single fit mode

Reported by: butler Owned by: butler
Priority: minor Milestone: SasView 4.2.0
Component: SasView Keywords:
Cc: Work Package: SasView Bug Fixing

Description

In the process of testing the 4.0 beta1 release, I have done some extensive testing with 466, 468 and 477 windows builds (Aug 25, Aug 30 and Sep 2, 2016 ESS builds - Aug 30 being the beta1 release date) and found a a small problem with the logic that allows the "chain fitting" to be active on a fit page until the batch fit tab is brought in focus then back to the fit tab at which point it is almost always greyed out again.

While this points to some convoluted logic in the GUI that could lead to more serious issues and should be cleaned up, I was unable to find anything more serious. Thus since the deconvoluting of the GUI code necessary is probably a bigger code change than one would like at this point in the release cycle, and since the functionality does not seem impaired, I am making this a +1 ticket with a minor Priority level.

Change History (2)

comment:1 Changed 21 months ago by butler

  • Milestone changed from SasView Next Release +1 to SasView 4.2.0
  • Owner set to butler
  • Status changed from new to assigned

Tested on 4.2 2b master branch and unless the behavior is slightly different in some subtle way this is mostly desired behavior. The fit button on the FitpPage will do a single fit only (the one attached to that page) and whenever the FitPage is in focus the "chain fitting" is not active (greyed out). Whenever the focus is changed to the BatchPage the "chain fitting" becomes active. went back and forth a few times and seems fine.

comment:2 Changed 21 months ago by butler

  • Resolution set to fixed
  • Status changed from assigned to closed

Given the behavior seen now seems to be appropriate, am going to close this ticket. If there is some remaining subtlety found later a new ticket that describes the specific issue should be created.

Note: See TracTickets for help on using tickets.