#3429 closed enhancement (fixed)
[patch] [cla] Tooltip: support multiple node ids in the connectId attribute
| Reported by: | cameron | Owned by: | bill |
|---|---|---|---|
| Priority: | high | Milestone: | 1.0 |
| Component: | Dijit | Version: | 0.9 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Attachments (1)
Change History (5)
Changed 12 years ago by
| Attachment: | Tooltip-multiple-connectId.patch added |
|---|
comment:2 Changed 12 years ago by
| Component: | General → Dijit |
|---|---|
| Milestone: | → 1.0 |
| Owner: | changed from anonymous to bill |
| Reporter: | changed from guest to cameron |
| Summary: | Patch for Tooltip to support multiple node ids in the connectId attribute → [patch] [cla] Tooltip: support multiple node ids in the connectId attribute |
| Type: | defect → enhancement |
comment:3 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 Changed 10 years ago by
(In [16565]) [10942] left the Tooltip API in a confusing state since it converted the connectId parameter (which sounds like a scalar) into an array. For back-compatibility and slightly less confusion, make programmatic instantiation and Tooltip.attr('connectId', ...) accept both arrays and scalars.
For 2.0 I want to just rename that connectId to connectIds, or convert it back to a scalar. (How often do we want a single tooltip for multiple nodes? It seems uncommon.)
Along the way I noticed that Tooltip.attr('connectId', ...) doesn't work correctly since it doesn't erase the old connections. Not sure that's worth supporting anyway though; it too seems quite uncommon.
Note: See
TracTickets for help on using
tickets.
cameron@… : adding patch