{"action":"created","issue":{"url":"https://api.github.com/repos/heitzmann/gdspy/issues/61","repository_url":"https://api.github.com/repos/heitzmann/gdspy","labels_url":"https://api.github.com/repos/heitzmann/gdspy/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/heitzmann/gdspy/issues/61/comments","events_url":"https://api.github.com/repos/heitzmann/gdspy/issues/61/events","html_url":"https://github.com/heitzmann/gdspy/issues/61","id":346180565,"node_id":"MDU6SXNzdWUzNDYxODA1NjU=","number":61,"title":"Path widths not conserved for number_of_paths higher than 1","user":{"login":"dwaardenburg","id":27302388,"node_id":"MDQ6VXNlcjI3MzAyMzg4","avatar_url":"https://avatars3.githubusercontent.com/u/27302388?v=4","gravatar_id":"","url":"https://api.github.com/users/dwaardenburg","html_url":"https://github.com/dwaardenburg","followers_url":"https://api.github.com/users/dwaardenburg/followers","following_url":"https://api.github.com/users/dwaardenburg/following{/other_user}","gists_url":"https://api.github.com/users/dwaardenburg/gists{/gist_id}","starred_url":"https://api.github.com/users/dwaardenburg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dwaardenburg/subscriptions","organizations_url":"https://api.github.com/users/dwaardenburg/orgs","repos_url":"https://api.github.com/users/dwaardenburg/repos","events_url":"https://api.github.com/users/dwaardenburg/events{/privacy}","received_events_url":"https://api.github.com/users/dwaardenburg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-07-31T13:10:22Z","updated_at":"2018-07-31T16:17:22Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I noticed that when I use a number_of_paths higher than 1 when I change the path distance between the paths this does not conserve the widths of the paths it draws. Only the widths of the paths at the beginning and the end of the tapered section. I would say that these two parameters could be simultaneously the width of the line and would strongly suggest this should be fixed, as for the effect can be difficult to observe but lead to errors none the less."},"comment":{"url":"https://api.github.com/repos/heitzmann/gdspy/issues/comments/409279837","html_url":"https://github.com/heitzmann/gdspy/issues/61#issuecomment-409279837","issue_url":"https://api.github.com/repos/heitzmann/gdspy/issues/61","id":409279837,"node_id":"MDEyOklzc3VlQ29tbWVudDQwOTI3OTgzNw==","user":{"login":"dwaardenburg","id":27302388,"node_id":"MDQ6VXNlcjI3MzAyMzg4","avatar_url":"https://avatars3.githubusercontent.com/u/27302388?v=4","gravatar_id":"","url":"https://api.github.com/users/dwaardenburg","html_url":"https://github.com/dwaardenburg","followers_url":"https://api.github.com/users/dwaardenburg/followers","following_url":"https://api.github.com/users/dwaardenburg/following{/other_user}","gists_url":"https://api.github.com/users/dwaardenburg/gists{/gist_id}","starred_url":"https://api.github.com/users/dwaardenburg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dwaardenburg/subscriptions","organizations_url":"https://api.github.com/users/dwaardenburg/orgs","repos_url":"https://api.github.com/users/dwaardenburg/repos","events_url":"https://api.github.com/users/dwaardenburg/events{/privacy}","received_events_url":"https://api.github.com/users/dwaardenburg/received_events","type":"User","site_admin":false},"created_at":"2018-07-31T16:17:22Z","updated_at":"2018-07-31T16:17:22Z","author_association":"CONTRIBUTOR","body":"After having thought about it for a little longer it would indeed be a very difficult thing to solve. However, I still think there is an definite need for solving this as the code suggest that the correct width is obeyed. That is not the case. \r\n\r\nSo far I have a couple of suggestions:\r\n - I would think we only need to know the direction and the width of the old path and the new path to solve the problem with a boolean operation.  This would then allow some sort of fix depending on what dimensions are most critical (I would say that would be width as length of paths can be fixed in other locations). The turning of multiple paths does not have this problem \r\n<img width=\"131\" alt=\"screen shot 2018-07-31 at 18 05 07\" src=\"https://user-images.githubusercontent.com/27302388/43471884-69096256-94ec-11e8-90fd-eac62ce9196f.png\"> This however makes conserving math lengths very difficult, but conserves path widths if I see it correctly. None the less, I would suggest that we look for the solution in that code.\r\n- The more simple thing is to just warn the user that the widths/lengths are not conserved.\r\n\r\nI am currently working on a solution for my device by just drawing each path separately and fixing the gaps in the corners by just making both polygons longer on the side that is coming short.\r\n\r\nIf I have more information I will come back to you..."}}
{"actor":{"display_login":"dwaardenburg"}}