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.
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
Re-factor qSlicerIO code #3322
Milestone
Comments
lassoan
added a commit
to lassoan/Slicer
that referenced
this issue
Jun 2, 2023
When a file with a generic extensions was drag-and-dropped to the application window (e.g., .nrrd, .json, .txt) then the default "Description" for each file depended on the order of reader plugin registration. This commit adds logic that to colors, markups, segmentations, sequences, tables, terminologies file readers to have a very quick look into the file content (not parsing, just reading the first few hundred bytes and search for some constant text) to get a confidence value that the reader is the most suitable for that file. fixes Slicer#3322
lassoan
added a commit
to lassoan/Slicer
that referenced
this issue
Jun 2, 2023
When a file with a generic extensions was drag-and-dropped to the application window (e.g., .nrrd, .json, .txt) then the default "Description" for each file depended on the order of reader plugin registration. This commit adds logic that to colors, markups, segmentations, sequences, tables, terminologies file readers to have a very quick look into the file content (not parsing, just reading the first few hundred bytes and search for some constant text) to get a confidence value that the reader is the most suitable for that file. fixes Slicer#3322
stephencrowell
pushed a commit
to stephencrowell/Slicer
that referenced
this issue
Jun 29, 2023
When a file with a generic extensions was drag-and-dropped to the application window (e.g., .nrrd, .json, .txt) then the default "Description" for each file depended on the order of reader plugin registration. This commit adds logic that to colors, markups, segmentations, sequences, tables, terminologies file readers to have a very quick look into the file content (not parsing, just reading the first few hundred bytes and search for some constant text) to get a confidence value that the reader is the most suitable for that file. fixes Slicer#3322
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The text was updated successfully, but these errors were encountered: