Rse viewer

[erezcoh4]

No description provided.

[erezcoh4]

refined R/S/E navigation and synced ROI with RGB images

[drinkingkazu]

Should we evaluate this branch? Help resolving conflicts etc.?
@erezcoh4 feel free to tag others as participants. I tag myself. If you can specify some specific things (like I asked above) then I'm happy to help.

[vgenty]

Yes we should evaluate, I think i see some binary files committed to this branch such as w/ this commit 417ea31. In addition there are some hard coded paths we need to address present in this commit 8add435

[erezcoh4]

thanks @vgenty and @drinkingkazu
the hard-coded paths make it easier for me to load the (same) ROI file i use every time.
I plan (when i have time....) to add a loading widget that will prevent the user from having to type the full path every time he wants to load the ROI file, and change the production widget to a pop-up list. does this make sense?

[twongjirad]

though I understand the hardcoded paths are useful to you, develop is for everyone. and everyone uses the ROI tools for hand-scanning. in order to merge into develop, those need to be removed.

[erezcoh4]

hhh, i didn't mean that we should keep these paths of course... just meant to explain myself; i'll remove them of course... sorry

[twongjirad]

Oh, sorry! I misunderstood. Thanks!