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

Classic DLL Vs. New version #2

Closed
ghost opened this issue Aug 26, 2012 · 4 comments
Closed

Classic DLL Vs. New version #2

ghost opened this issue Aug 26, 2012 · 4 comments

Comments

@ghost
Copy link

ghost commented Aug 26, 2012

Hi,
The new dll missing EvilDicom.Components. Are you planning to add this class?

The second question: I can open DICOM CAD images, how can I play or advance the frames? Would you have a .Net sample, that will be greatly appreciated.

Thanks

@rexcardan
Copy link
Owner

Hi, I realize your possible frustration with the change in libraries. The first Evil DICOM library was a test framework for me to build out the core functionality of DICOM in C#. Unfortunately, it was slow and overly complicated. It really needed to be totally rewritten. Which part of the Components namespace are you wanting?

On the CAD image functionality, could you send me a sample image so that I can incorporate this into the image processing (which is currently missing in the new library)? My email is r + my lastname + @uabmc.edu.

@ghost
Copy link
Author

ghost commented Sep 20, 2012

Thanks

@rexcardan
Copy link
Owner

Ok, I have looked at your file. The next version of Evil DICOM can open it (it won't let me commit the new one yet), but I noticed the image part of the file is encoded in JPEG. Unfortunately, even the old Evil DICOM doesn't support compression. The refresh doesn't have image functionality at all yet, but it can read your file and spit out the bits in the image part. What to do with those bits though is relatively complicated just to get the image that you want to see. That is why it has been left out of previous versions of the library. Are you just looking for a viewer? ED is really designed as an application framework for reading an manipulating DICOM files.

@ghost
Copy link
Author

ghost commented Sep 25, 2012

Thanks Rex, at present our application is designed to view the image and associated data (as your explorer). For CAD images, I converted them into JEPG files and can display them, not the best solution but will do for now. Any target dates for the next version of ED! Please keep me posted.

Regards

Hesham

From: rexcardan [mailto:notifications@github.com]
Sent: Monday, September 24, 2012 8:10 PM
To: rexcardan/Evil-DICOM
Cc: user373721
Subject: Re: [Evil-DICOM] Classic DLL Vs. New version (#2)

Ok, I have looked at your file. The next version of Evil DICOM can open it (it won't let me commit the new one yet), but I noticed the image part of the file is encoded in JPEG. Unfortunately, even the old Evil DICOM doesn't support compression. The refresh doesn't have image functionality at all yet, but it can read your file and spit out the bits in the image part. What to do with those bits though is relatively complicated just to get the image that you want to see. That is why it has been left out of previous versions of the library. Are you just looking for a viewer? ED is really designed as an application framework for reading an manipulating DICOM files.


Reply to this email directly or view it on GitHub #2 (comment) .

Image removed by sender.

rexcardan pushed a commit that referenced this issue Oct 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant