{"action":"created","issue":{"url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1856","repository_url":"https://api.github.com/repos/HaxeFlixel/flixel","labels_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1856/labels{/name}","comments_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1856/comments","events_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1856/events","html_url":"https://github.com/HaxeFlixel/flixel/issues/1856","id":154908980,"number":1856,"title":"Use a FlxPoint for position instead of separate x and y variables","user":{"login":"Tiago-Ling","id":1617118,"avatar_url":"https://avatars.githubusercontent.com/u/1617118?v=3","gravatar_id":"","url":"https://api.github.com/users/Tiago-Ling","html_url":"https://github.com/Tiago-Ling","followers_url":"https://api.github.com/users/Tiago-Ling/followers","following_url":"https://api.github.com/users/Tiago-Ling/following{/other_user}","gists_url":"https://api.github.com/users/Tiago-Ling/gists{/gist_id}","starred_url":"https://api.github.com/users/Tiago-Ling/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Tiago-Ling/subscriptions","organizations_url":"https://api.github.com/users/Tiago-Ling/orgs","repos_url":"https://api.github.com/users/Tiago-Ling/repos","events_url":"https://api.github.com/users/Tiago-Ling/events{/privacy}","received_events_url":"https://api.github.com/users/Tiago-Ling/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/HaxeFlixel/flixel/labels/New%20Feature","name":"New Feature","color":"009800"},{"url":"https://api.github.com/repos/HaxeFlixel/flixel/labels/Structure","name":"Structure","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-05-15T13:35:10Z","updated_at":"2016-05-15T15:31:27Z","closed_at":null,"body":"This would allow to use vector operations on sprites / objects position out of the box. To avoid any breaking changes we can use a getter and setter for x and y which would modify `position.x` and `position.y`. It'd be transparent for users and for the framework internals. \r\n\r\nAnother step for this would be doing what @Beeblerox proposed: merging FlxVector into FlxPoint so users could benefit from the useful vector methods there.\r\n\r\n\r\n\r\n<bountysource-plugin>\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34248365-use-a-flxpoint-for-position-instead-of-separate-x-and-y-variables?utm_campaign=plugin&utm_content=tracker%2F254189&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F254189&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/comments/219292393","html_url":"https://github.com/HaxeFlixel/flixel/issues/1856#issuecomment-219292393","issue_url":"https://api.github.com/repos/HaxeFlixel/flixel/issues/1856","id":219292393,"user":{"login":"Beeblerox","id":857406,"avatar_url":"https://avatars.githubusercontent.com/u/857406?v=3","gravatar_id":"","url":"https://api.github.com/users/Beeblerox","html_url":"https://github.com/Beeblerox","followers_url":"https://api.github.com/users/Beeblerox/followers","following_url":"https://api.github.com/users/Beeblerox/following{/other_user}","gists_url":"https://api.github.com/users/Beeblerox/gists{/gist_id}","starred_url":"https://api.github.com/users/Beeblerox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Beeblerox/subscriptions","organizations_url":"https://api.github.com/users/Beeblerox/orgs","repos_url":"https://api.github.com/users/Beeblerox/repos","events_url":"https://api.github.com/users/Beeblerox/events{/privacy}","received_events_url":"https://api.github.com/users/Beeblerox/received_events","type":"User","site_admin":false},"created_at":"2016-05-15T15:31:27Z","updated_at":"2016-05-15T15:31:27Z","body":"@Gama11 changed position will be already there, i'm only talking about timing heavy calculations: do them only then they are required, not every time we change some value. But this will require many new checks (if position or scale or offset or origin or something else is dirty)"}}