You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Importing objects from a .qpdata file containing TMA cores can result in the cores being brought over, but not properly assigned to a TMA grid. As a result, they are 'selectable' and appear under the 'Hierarchy' tab, but are otherwise not visible.
To Reproduce
Steps to reproduce the behavior:
Create a project with 2 images
Add a TMA grid to one (e.g. Specify TMA grid)
Save the data
Open the second image
Drag the .qpdata file from the first image onto the QuPath viewer
See the weird hierarchy behavior
Expected behavior
If there is a TMA grid on the second image already, offer to replace it with the one from the .qpdata file
If there is no TMA grid on the second image, import it 'properly'
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Bug report
Describe the bug
Importing objects from a
.qpdata
file containing TMA cores can result in the cores being brought over, but not properly assigned to a TMA grid. As a result, they are 'selectable' and appear under the 'Hierarchy' tab, but are otherwise not visible.To Reproduce
Steps to reproduce the behavior:
.qpdata
file from the first image onto the QuPath viewerExpected behavior
.qpdata
fileScreenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
See https://forum.image.sc/t/tma-core-missing/85571
The text was updated successfully, but these errors were encountered: