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

Legacy layer does not support virtual stacks #4

Closed
ctrueden opened this Issue May 3, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@ctrueden
Copy link
Member

commented May 3, 2014

There are a couple legacy plugins that open data as virtual stacks (File > Import > Stack From List and File > Import > TIFF Virtual Stack). However IJ2 will try to create memory resident stacks from the resulting ImagePluses. The legacy layer should detect when a legacy created ImagePlus is backed by a virtual stack and create an Img that is also of a virtual type.

Migrated-From: http://trac.imagej.net/ticket/1767

@bdezonia

This comment has been minimized.

Copy link
Member

commented May 3, 2014

I'm pretty sure I fixed this one before I left. Can you retest?

@dscho

This comment has been minimized.

Copy link
Member

commented May 3, 2014

I will, in the course of the work after uploading a new ImageJ2 (which required quite a few preparations in fiji-compat, Fiji_Updater and imagej-launcher). I also vaguely remember that this was fixed, but we still need to reconcile imglib2-ij with imagej-legacy... So all of this might be fixed in one monster flurry of commits.

@dscho dscho added this to the imagej-2.0.0 milestone May 26, 2014

@dscho

This comment has been minimized.

Copy link
Member

commented May 30, 2014

I did not have time to re-test, but I saw the code. So I am closing it!

@dscho dscho closed this May 30, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.