Community
Participate
Working Groups
In the Navigator, a user might use the checkbox to tick off 1 or more items, then move the mouse to a non-selected item, popup the menu and see the tooltip "Delete the selected files or folders". But really it's just the item you used the triangle popdown on, not the selected items. Either simply rename the tooltips to be more generic "item(s)" or there needs to be a callback to set the tooltip text before displaying it.
Currently the method in which tooltips are provided and the fact that the commands are linked to this page this will have to be revisited after 0.4.
command.tooltip could be extended to either: static text (like today) or tooltipCallback a function that returns a context appropriate tooltip, such as function(data) {return "the most appropriate tooltip ever for " + data.items.Location;} I think the main thing to be wary of is that it should be a synchronous return, so we wouldn't expose this to command service extensions, it would be mostly for our internal commands. A separate piece of work (if needed) would be extending the support to plug-ins by having the code that maps extension points to commands do the work for it. It would require some kind of "describable" expression or parsing in the plugin properties that the extension mappings could read in order to produce the function. (kind of how we handle validationProperties->visibleWhen today).y support this if we ha
(In reply to comment #2) >(kind of how we handle validationProperties->visibleWhen today).y > support this if we ha "kind of how we handle mapping validationProperties->visibleWhen function today" (ignore garbled text). I annotated bug 370903 to capture this use case.
I just noticed the git commands use a little trick...they reset the tooltip when visibleWhen is executed. This lets them put things like current branch name, in the tooltip. We may want to recommend this as the actual pattern. Because that is where you are going to know if you have one or more items, or which ones, etc.
moving out of 0.5M2 to 0.5 milestone until we have more specific buckets for future
I think we can consider this fixed by virtue of moving the "context menu" actions in the navigator to the selection menu. So there's no longer confusion about which items you are working with.
