Fix annoying little UI behavior things

[joewheaton]

The new QRAVE 0.6 is really cool. There were at least six steps forward but a few steps back. There are some lingering issues as well as some new issues that are only getting revealed now that we have more projects. Here are the things I am noticing after putting it through quite a few paces. Collectively these things are in the "minor annoyances with work-arounds, but adding up to a lot of wasted time for QRAVE users".

@philipbaileynar and @MattReimer you should both watch above. Happy to chat if anything doesn't make sense. Some of what is below are easy fixes (a few may not be). I have tried to list out what issues and fixes I think might come from the video.

• 1. Fix Adding Default Layers when multiple projects open.

• 2. If you accidently open a project that happens to be open, nothing visibly happens.
  This would be a nice one to at least warn the user that the project is already open in their RAVE Project Explorer.

• 3. When you open a project and other projects are open, add to top of explorer tree, not bottom. Open New Projects At Top of Project Tree #59

Same Project Name - Poor Handling and Non-Existent Notifications/Recognition

• 4. Project Names should be more distinctive (okay this should really migrate to warehouse repo, but it is important). Fix project names (not necessarily to be unique, but more distinctive)

• 5. If you open two distinct projects (i.e. unique guids) but of same name and type, it does not do what is asked. Fix by checking if a project is already open of same name Opening two projects with the same name #60
  If a project is found of same name, a) Warn user "A distinctive project of same name is already loaded in RAVE." , b) Suggest a renamed "Label" for that session only (e.g. ChannelAREA HUC 09909000 to ChannelAREA HUC 09909000 - 01 and allow them to overwrite.

• 6. Add a right-click at project level in RAVE to Rename Project Label (in this session only).
  This would overcome a lot of issues because the way RAVE works is it uses that project label to both Add contents to the Layer Manager (TOC) and to provide the name label in the TOC tree. It would not be something that makes any changes to the project and it would only be something recognized in that current RAVE session.

• 7. If a project of same name has already been added to map, it is overwriting the table of contents in the layer manager.
  5 and 6 would fix this.

• 8. Workarounds are not elegant (e.g. renaming group) because then you can't add layers to that project any more.

• 9. When I try to add something to the map that RAVE thinks is already there, warn that it thinks it is already there and ask if you want to replace.

You might notice grumblings in video related to existing issues: #49, #47, especially #32, #19,

[MattReimer]

These are excellent. Thanks for catching all these Joe!

[joewheaton]

Always happy to be a pain in the backside....

[philipbaileynar]

items 3 and 5 above are now broken out into dedicated issues for milestone QRAVE 0.7.

I am removing this ticket from QRAVE 0.7 because all other features are being pushed to future versions.

[joewheaton]

Just drawing attention to these issues again as we think about updates to QRAVE for compatibility with warehouse 3.X and QRiS.