Ticket #1141 (new enhancement)

Opened 7 years ago

Last modified 6 years ago

Copy To System enhancement

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-unscheduled
Component: Plugins Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1632

Description

At one time Adam Fraser mentioned that it would be nice if the Copy command would also quietly run the CopyToSystem plugin. To do so we need to write a pure IJ2 version of the Copy command. With the existence of LegacyService::runLegacyPlugin() this pure IJ2 implementation could be quite easy to implement. It would run the legacy Copy command and then run the IJ2 CopyToSystem plugin,

Change History

comment:1 Changed 7 years ago by dscho

There have been reported problems with CopyToSystem. Note: I think that Copy should run CopyToSystem, too, but it would be good to identify the problems, too.

The email thread I am referring to is:  http://imagej.1557.n6.nabble.com/Copy-to-System-td4633650.html

comment:2 Changed 7 years ago by bdezonia

  • Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4

comment:3 Changed 7 years ago by bdezonia

  • Blocking 1333 added

comment:4 Changed 7 years ago by bdezonia

  • Blocking 1460 added; 1333 removed
  • Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5

comment:5 Changed 7 years ago by bdezonia

I think we want to avoid legacy service here. We should do our own copy/cut/paste with different internal buffers (for images, results tables, etc.). This would allow all types of (for instance, pixel) data to be fully copied/pasted rather than legacy translated data values.

comment:6 Changed 6 years ago by bdezonia

  • Blocking 1632 added; 1460 removed
  • Milestone changed from imagej2-b7-ndim-data to imagej2-unscheduled
Note: See TracTickets for help on using tickets.