Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

file->open .csv files creates badly named variables #90

Closed
gdementen opened this issue Oct 11, 2017 · 0 comments
Closed

file->open .csv files creates badly named variables #90

gdementen opened this issue Oct 11, 2017 · 0 comments
Assignees
@gdementen
Labels
bug priority: high

Comments

@gdementen
Copy link
Collaborator

The variables are named with the full path, eg:

c:/tmp/a.csv
c:/tmp/b.csv

instead of simply a and b.

which are almost useless because you cannot do anything with them in the console.
@gdementen gdementen self-assigned this Oct 12, 2017
gdementen added a commit to gdementen/larray-editor that referenced this issue Oct 13, 2017
@gdementen
* fixed opening files via file->open. It crashed in update_title beca…
89e5ea5 
…use it was called a first time with array=None, and the dtype = array.dtype.name line crashed.

* opening .csv files in the editor will create variables with only the filename without extension (instead of the variables named by the full path). Closes larray-project#90.
* moved unsaved marker just before filename (this is more standard)
* .csv files will display as "dir\fname.csv - axes_info" instead of dir\fname.csv - fname
* other files will display as "fname.ext - array_name: axes_info" instead of using the full path
* when there is no current file, use <new> as the filename
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gdementen gdementen

Labels
bug priority: high
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gdementen