Ticket #5433 (closed: worksforme)

Opened 8 years ago

Last modified 5 years ago

Clicking Apply/OK in the user preferences after typing an invalid directory throws an exception.

Reported by: Robert Whitley Owned by: Russell Taylor
Priority: major Milestone: Release 2.2
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Peter Parker

Description

When you type an invalid directory into Mantid user preferences it throws an exception saying file not found and asks the user to terminate or continue.

Once this message has appeared and you go back to the correct path it will throw the same exception and then if you click again it will save.

This isn't used often because browse buttons help the user pick the correct directory.

N.B. This only applies to Mantid->Directories and not General->File Locations

Change History

comment:1 Changed 8 years ago by Russell Taylor

  • Owner set to Russell Taylor
  • Status changed from new to assigned

comment:2 Changed 8 years ago by Alex Buts

The problem described by ticket #5271 is still present in Matid 2.1.1 patch release. Have observed it on Friday on old user's 32 bit Win machine and my 64-bit behaves as before.

There is the description copied from the ticket #5271, still the same as before:

Start MantidPlot

Select view->preferences->mantid->directories.

Using directory browser choose new directory to look for users python scripts

Press apply.

An exception is thrown that the file does not exist

After selecting -> continue working and Apply two more times exception disappears and the path is set.

Tested on Mantid freshly installed on new machine. Does not happen on my developer's machine.

Annoying!

comment:3 Changed 8 years ago by Russell Taylor

  • Status changed from assigned to accepted

comment:4 Changed 8 years ago by Russell Taylor

  • Status changed from accepted to verify
  • Resolution set to worksforme

I don't see this - I get a log message saying that the directory doesn't exist, but not exceptions.
Checked this on Windows & Mac installed versions & RHEL6 locally-built.

Regarding Alex's comment - the fix for this accidentally didn't make it into the patch release branch, but is in the master branch.

comment:5 Changed 8 years ago by Peter Parker

  • Status changed from verify to verifying
  • Tester set to Peter Parker

comment:6 Changed 8 years ago by Peter Parker

I also don't see the exception - an error message is now reported to log.

The problem in comment 2 is now also fixed.

comment:7 Changed 8 years ago by Peter Parker

  • Status changed from verifying to closed

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 6279

Note: See TracTickets for help on using tickets.