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.

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

Closed
slicerbot opened this issue Mar 13, 2020 · 0 comments
Closed

Re-factor qSlicerIO code #3322

slicerbot opened this issue Mar 13, 2020 · 0 comments
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@lassoan lassoan added this to the Backlog milestone Mar 16, 2020
@lassoan lassoan removed the backlog label Mar 16, 2020
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
@lassoan lassoan closed this as completed in 5204e7a Jun 8, 2023
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
Labels
None yet
Development

No branches or pull requests

2 participants