search

pombreda / dicompyler

Automatically exported from code.google.com/p/dicompyler
0 stars 0 forks source link

Four pane view #65

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
This is not a sore point type issue, but more a roadmap issue. I was trying to 
look at sagittal CTs today (dicompyler is the only DICOM CT-viewer I have on my 
home box) and found that the handling of these images was OK for display, but 
out of order and when it came to re-sizing, there was a lot of processor use 
(one core maxed out for 2-3 minutes) unlike re-sizing the axials which is near 
instantaneous. Obviously there was no cross hair localisation either (centering 
on a common x,y,z co-ordinate)

A

Original issue reported on code.google.com by alexisan...@gmail.com on 3 Jan 2012 at 12:34

GoogleCodeExporter commented 9 years ago 
4 pane view is on the roadmap, but hasn't been listed yet. The eventual goal is 
to switchover to VTK for 2D/3D rendering, however for the time being the 
current rendering method will have to suffice.

Lots of these features (i.e. localization, orientation markers, etc.) would be 
included with the VTK rendering.

Original comment by bastula on 14 Mar 2012 at 3:26