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
Potential enhancements @davidborland and I discussed on 2022-05-18, in no particular order
Slice and ID numbers (potentially add flags per current slice, with a summary table)
Flags for dialogue
Continuity between feedback dialog (region ID refs) and region IDs (IDs will likely not be reused based on how Hong will implement) – also, some ninjas will erase or delete ID and restart (same ID remains if erase to 0 pixels, but a new one is generated if ‘remove ID’); example of potential mismatch between feedback and region ID: when a ninja merges one ID with another (if that ID number is then assigned to a new region with a different ninja, that may create confusion between multiple sensei reviewers)
Plane axis IDs (x,y,z) – can leave out for now
For region ID, include if already claimed in another user’s assignment- per @davidborland , update in progress, but current solution is offline communication between ninjas for potential claiming conflicts
Undo button for claimed regions
Ability to toggle boundary overlay - done
Navigation features (pan, zoom in/out) in 2D while still keeping the 2D and 3D views decoupled
Shortcut keys - presently only ctrl, can add L/R arrow keys to change tool size and up/down to toggle between slices
Documentation of features- would be great to be able to generate a printable pdf, specifically for navigation and edit features
Progress dashboards for users, reviewers, admins
Ability to change colors of boundaries for both engagement and to discern state of nucleus (refining/done/verified)
Long-term preference post-completed dev version: ability to edit in 3D
The text was updated successfully, but these errors were encountered:
@JustKeepClimbing Changed this to a checklist and marked those that I think are completed. May be worth revisiting, and creating separate issues for those we still need (e.g. we already have an issue for 3D editing).
Potential enhancements @davidborland and I discussed on 2022-05-18, in no particular order
The text was updated successfully, but these errors were encountered: