{"action":"created","issue":{"url":"https://api.github.com/repos/OneZoom/OZtree/issues/111","repository_url":"https://api.github.com/repos/OneZoom/OZtree","labels_url":"https://api.github.com/repos/OneZoom/OZtree/issues/111/labels{/name}","comments_url":"https://api.github.com/repos/OneZoom/OZtree/issues/111/comments","events_url":"https://api.github.com/repos/OneZoom/OZtree/issues/111/events","html_url":"https://github.com/OneZoom/OZtree/issues/111","id":335349620,"node_id":"MDU6SXNzdWUzMzUzNDk2MjA=","number":111,"title":"Zooming into high-branched areas results in a moosh of signposts","user":{"login":"lentinj","id":586911,"node_id":"MDQ6VXNlcjU4NjkxMQ==","avatar_url":"https://avatars2.githubusercontent.com/u/586911?v=4","gravatar_id":"","url":"https://api.github.com/users/lentinj","html_url":"https://github.com/lentinj","followers_url":"https://api.github.com/users/lentinj/followers","following_url":"https://api.github.com/users/lentinj/following{/other_user}","gists_url":"https://api.github.com/users/lentinj/gists{/gist_id}","starred_url":"https://api.github.com/users/lentinj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lentinj/subscriptions","organizations_url":"https://api.github.com/users/lentinj/orgs","repos_url":"https://api.github.com/users/lentinj/repos","events_url":"https://api.github.com/users/lentinj/events{/privacy}","received_events_url":"https://api.github.com/users/lentinj/received_events","type":"User","site_admin":false},"labels":[{"id":927428524,"node_id":"MDU6TGFiZWw5Mjc0Mjg1MjQ=","url":"https://api.github.com/repos/OneZoom/OZtree/labels/Version%203.3","name":"Version 3.3","color":"e99695","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-06-25T10:32:36Z","updated_at":"2018-09-06T20:34:50Z","closed_at":null,"author_association":"COLLABORATOR","body":"![image](https://user-images.githubusercontent.com/586911/41845394-3da6c40c-786b-11e8-9d79-42d2478aa4af.png)\r\n\r\nJust disable signpost when there's lots of branching? We could do some fancy logic to avoid overlapping signposts, but even if we had a few signposts at this point, it won't be obvious what they're pointing at."},"comment":{"url":"https://api.github.com/repos/OneZoom/OZtree/issues/comments/419232200","html_url":"https://github.com/OneZoom/OZtree/issues/111#issuecomment-419232200","issue_url":"https://api.github.com/repos/OneZoom/OZtree/issues/111","id":419232200,"node_id":"MDEyOklzc3VlQ29tbWVudDQxOTIzMjIwMA==","user":{"login":"jrosindell","id":3009279,"node_id":"MDQ6VXNlcjMwMDkyNzk=","avatar_url":"https://avatars1.githubusercontent.com/u/3009279?v=4","gravatar_id":"","url":"https://api.github.com/users/jrosindell","html_url":"https://github.com/jrosindell","followers_url":"https://api.github.com/users/jrosindell/followers","following_url":"https://api.github.com/users/jrosindell/following{/other_user}","gists_url":"https://api.github.com/users/jrosindell/gists{/gist_id}","starred_url":"https://api.github.com/users/jrosindell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jrosindell/subscriptions","organizations_url":"https://api.github.com/users/jrosindell/orgs","repos_url":"https://api.github.com/users/jrosindell/repos","events_url":"https://api.github.com/users/jrosindell/events{/privacy}","received_events_url":"https://api.github.com/users/jrosindell/received_events","type":"User","site_admin":false},"created_at":"2018-09-06T20:34:50Z","updated_at":"2018-09-06T20:34:50Z","author_association":"MEMBER","body":"I think you're right about all this.  \r\n\r\nOne possible thought about the solution to this is to tweak the logic that decides where to stop when rippling down the tree and drawing signposts.  If children are not developed properly or don't have xvar/rvar for all children then you simply don't allow the signpost logic to ripple down and have the parent be the signpost instead.  At present signpost logic rippling is based entirely on signpost size - from memory this means if current signpost is too big the you ripple down.  Which is fine for bifurcating trees, but in polytomy trees you could have current signpost too big whilst child signposts are too small / undefined. Hence the logic should be updated to reflect this.\r\n\r\nMaybe in such cases allow the parent to show the signpost but reduce the size of it so that it doesn't totally dominate the area and instead appears underneath the (otherwise boring) fanning part of the massive polytomy.  So, in my 25th June example, the three signposts at the bottom would none of them be drawn and instead a single larger (but not that large!) signpost would be drawn for the parent node of those three.\r\n\r\nI hope I've explained this clearly enough - it's a complex business!"}}
{"actor":{"display_login":"jrosindell"}}