Extension > Send region to ImageJ sends RGB image with burned in overlays & objects about qupath

[petebankhead]

This should be fixed now in the next release, so that the visibility of an object is used to determine whether it is sent to ImageJ or not. This also includes whether cells are shown with their boundaries and/or nuclei.

Regarding converting to ImageJ selections, that should already happen. It should already be the case that the objects are sent as ImageJ Rois on top of an ImageJ overlay - so you can either remove the overlay, or send its Rois to the ROI manager. If you do the latter, you should also see that the names of the Rois have also been set according to their names/classifications within QuPath.

Also, the 'primary' selected object (i.e. the one that was currently active whenever the Extract region to ImageJ command was run) should automatically be converted to an ImageJ Roi and set as the active selection in ImageJ - unless it was a rectangle. There isn't really so much point in sending rectangles Rois, since they will simply occupy the whole image (and can easily be recreated in ImageJ if necessary with Edit → Selection → Select All) - but all non-rectangles should be transferred, as shown below.

Hopefully that works well enough to be suitably heroic...

[petebankhead]

I've now updated the documentation on using ImageJ with QuPath at https://github.com/qupath/qupath/wiki/Working-with-ImageJ

I'll close this issue now, but please reopen it if things aren't working as described. The use of visibility status to influence what is sent to ImageJ should be available in the v0.0.4 release of QuPath.