BUG: list not supporting blobs with same ID in different swimlanes (pairings)
Reported by Jonathan Lister | October 7th, 2010 @ 06:00 PM | in 0.8
To see: use the participants web app, having edited samples/declare-same.sh to use WEB-2 as well; create a sample blob; load scenario 1; observe that clicking on the list only lets you click on one line for an ID, even if it exists in more than one pairing.
Comments and changes to this ticket
-
Ben Hood October 8th, 2010 @ 07:00 PM
- State changed from “new” to “resolved”
- Milestone order changed from “28” to “0”
(from [f77bf06ce682caf7c315ce1e6a0418dca324c511]) Now the list highlights the correct lines on hover; previously it was highlighting the last cluster that appeared with the same timestamp. This has simplified some of the handling of objects.
The size of clusters above 10 events is fixed to grow continuously - 'max' is currently a useless measure as it is resulting in tiny blobs. Some overlapping is OK, so a better definition of max should be found. It's changed to allow growth to any radius now.
[[#116 state:resolved]] http://github.com/lshift/diffa/commit/f77bf06ce682caf7c315ce1e6a041...
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
People watching this ticket
- Nobody is watching this ticket.
Referenced by
-
116
BUG: list not supporting blobs with same ID in different swimlanes (pairings)
[[#116 state:resolved]]
http://github.com/lshift/diffa/c...