team notes

[caver456]

Allow for 'notes' for each team tab.

Display could be something like a row pinned to the top of the team's table; but that seems a bit odd for multiline notes. And/or maybe something that shows a multiline popup when hovered, similar to a tooltip (like the fleetsync filter button at the top right) or a Note on an Excel cell.

Entry method for now could just be direct typing by the operator, but, eventually could be automated e.g. list of team members, assignment name, etc, pulled from (or pushed from) plans console via some shared file that radiolog watches.

This came up when the operator found it handy to type in a list of names of individuals on each team, and needed to make it visually quickly accessible by prepending the entry with a line of equals signs or plus signs or such - but that still could require scrolling to see it.

[caver456]

• [x] team notes dialog
• [x] context menu entry to open team notes dialog
• [x] save team notes in run directory
• [x] load / restore team notes when needed
• [x] warn / offer to save before closing teamNotesDialog (or changing team in teamNotesDialog) if edits have been made
• [x] top-level hotkey to show teamNotesDialog (probably F10)
• [x] display of team notes (in addition to team notes dialog)
  • [x] tooltip on team tab
  • [x] pin on or show above first line of team log section (figure out best way to display multi-line notes on one line)
  • [x] click in pinned note (left click? right click? both) should allow editing, maybe just by raising the teamNotesDialog
  • [x] tooltip on pinned first line, to show multiline notes

Features that could be added later:

• [ ] allow view/restore of old versions of team notes ('view old version' is different than 'revert' which actually makes an old version into the new version)
• [ ] allow auto-population of team notes from other tools (plans console, caltopo, etc) - while preserving hand-typed notes

[caver456]

Some explanation is needed on the latest WIP (tooltips) commit on the branch for this issue.

Tab status colors are set (every second for every tab) from updateTeamTimers. This is done using setStyleSheet. This has worked fine for years.

But: if you add a tooltip on the tabButton, its style is inherited from the style of the tabButton. So, the tooltip's background color would be the same as its tab, based on status and/or blink state. That was pretty distracting! We just want a single simple consistent unchanging background for the tooltip - white is fine.

After a bunch of googling, turns out the best way to 'stop' that 'inheritance' is to set the style using an object selector.

Did some attempts setting the stylesheet of QToolTip, and setting the palette of the tabButton rather than using styleSheet, but no luck. There might be a solution in one of those methods, but, a couple of days of trying didn't yield success.

So - went with the object selector. That worked but required a few changes in various parts of the code.

Previously: tab.setStyleSheet('background:green') Now: tab.setStyleSheet('#tab_z_Team00001 { background:green }'

This leaves the tooltip with a white background, as desired.

[caver456]

Having a tough time deciding the best way to indicate that a given team has notes, and to allow pinning, without taking up real estate.

Maybe a dot in the tab label area? Above and to the right, like a superscript? Below the label as a dot or a tiny notes icon? These would serve as an indication that the team has notes; then a hover on the tab could open an actual popup with a 'pin' button. When pinned, the notes become a single line of text above the team table, also with an unpin button.

[caver456]

Maybe do the simple part first: show the single line of notes above the team table, since it sounds like that will be part of the plan no matter what.

[caver456]

Interesting note upon selecting 'Team Notes from team 2 context menu: This happens after typing text for team 1, then closing and not saving. Need to track this down...

[caver456]

figured that one out - probably. Going forward with possibly-final commit.