Problem opening newly created silk file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Yesterday I successfully (or so I thought) created a new silk file that I 
called 'Mbelime Claire? (is it a problem that there's a space in the file 
name?).
2. I saved the file to the 'Context under construction' folder.
3. I quit SILKin
4. This morning, I wanted to work on the silk file so started SILKin, went to 
File, clicked on 'open' and tried to load the file.

What is the expected output?
File would open and ask me to select user.

What do you see instead?
new window popped up: see attachment

Sharon

Original issue reported on code.google.com by idani_na...@yahoo.co.uk on 21 Oct 2011 at 8:41

Attachments:

• [problem opening Mbelime Claire.silk.tiff](https://storage.googleapis.com/google-code-attachments/silkin/issue-10/comment-0/problem opening Mbelime Claire.silk.tiff)

[GoogleCodeExporter]

I have asked Sharon for the SILK file that produced this error. She is super 
responsive, so a solution should be posted soon.

Original comment by garymorr...@verizon.net on 21 Oct 2011 at 3:43

[GoogleCodeExporter]

THE FILE PROBLEM:  This SILK file has a single dyad (kin term) in it: "n̄ 
nīi". It has some special characters in it, and that is fine. But it is "two 
words" without a comma intervening. Perhaps you meant to enter 2 kin terms in 
the box, or perhaps this is a single kin term with 2 components and you used a 
blank to separate them. Multiple terms (you may enter as many as you like) must 
be separated by commas. And terms that have multiple components must be joined 
by underscores ("_"), not blanks or dashes. That is why you got this 
(misleading) error message.

THE SILKIN PROBLEM: Clearly, the error message was not very informative. But 
the real problem is that I could have detected this "illegal entry" in the text 
box as soon as you entered it and dealt with the problem right there. I didn't 
-- I waited until the file was re-loaded. That is too late to prevent the 
problem.

I will create (or enlarge) an error-checking feature that runs while you are 
entering data and complains immediately. I will make you fix it right there. 

GOOD CATCH. I don't know if you deliberately created this test condition or 
just got lucky, but I'm glad you found it.

Original comment by garymorr...@verizon.net on 24 Oct 2011 at 2:42

• Changed state: Started

[GoogleCodeExporter]

Sent revised code to Sharon for verification.

Original comment by garymorr...@verizon.net on 4 Nov 2011 at 6:26

• Changed state: Fixed

[GoogleCodeExporter]

Issue 10 resolved

Original comment by idani_na...@yahoo.co.uk on 5 Nov 2011 at 8:05

[GoogleCodeExporter]

Original comment by garymorr...@verizon.net on 5 Nov 2011 at 9:33

• Changed state: Verified