This repo contains source code for TableView, originally developed by Jim Johnson and colleagues at the University of Minnesota. To view the original paper on TableView, click the wiki link. Developers in the Loraine lab are in the process of updating the code, posting documentation, and supporting TableView so that many more people can use it.
Currently when users use File/URL open to open a new data set, the Field Separator is TAB.
However, if user tries to load a file and the file is actually comma-separated, TV is smart enough to recognize that it shouldn't use a tab as the delimiter, even though that option is selected.
Yay TableView! What a smart program it is.
However, this is is a little confusing for users who might be paying attention to the GUI.
So..
Add a new option to be checked by default that says: "TableView's best guess".
However, if the user does insist on selecting a different delimiter, TableView should honor their selection no matter how wrong it may seem.
Who knows? Some-one working with a tab-delimited file may wish for all the values (the entire line) to go into one field. It could happen. But more importantly, TV should behave in a fashion that can be easily intuited and predicted by the user when he or she looks at the UI.
This pertains to TV 1.4. Don't bother to change this on the 1.3 branch.
Currently when users use File/URL open to open a new data set, the Field Separator is TAB.
However, if user tries to load a file and the file is actually comma-separated, TV is smart enough to recognize that it shouldn't use a tab as the delimiter, even though that option is selected.
Yay TableView! What a smart program it is.
However, this is is a little confusing for users who might be paying attention to the GUI.
So..
Add a new option to be checked by default that says: "TableView's best guess".
However, if the user does insist on selecting a different delimiter, TableView should honor their selection no matter how wrong it may seem.
Who knows? Some-one working with a tab-delimited file may wish for all the values (the entire line) to go into one field. It could happen. But more importantly, TV should behave in a fashion that can be easily intuited and predicted by the user when he or she looks at the UI.
This pertains to TV 1.4. Don't bother to change this on the 1.3 branch.