{"action":"opened","issue":{"url":"https://api.github.com/repos/foosel/OctoPrint/issues/923","labels_url":"https://api.github.com/repos/foosel/OctoPrint/issues/923/labels{/name}","comments_url":"https://api.github.com/repos/foosel/OctoPrint/issues/923/comments","events_url":"https://api.github.com/repos/foosel/OctoPrint/issues/923/events","html_url":"https://github.com/foosel/OctoPrint/issues/923","id":84602671,"number":923,"title":"Separate movement amounts for Z and XY","user":{"login":"chickenchuck040","id":1933593,"avatar_url":"https://avatars.githubusercontent.com/u/1933593?v=3","gravatar_id":"","url":"https://api.github.com/users/chickenchuck040","html_url":"https://github.com/chickenchuck040","followers_url":"https://api.github.com/users/chickenchuck040/followers","following_url":"https://api.github.com/users/chickenchuck040/following{/other_user}","gists_url":"https://api.github.com/users/chickenchuck040/gists{/gist_id}","starred_url":"https://api.github.com/users/chickenchuck040/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chickenchuck040/subscriptions","organizations_url":"https://api.github.com/users/chickenchuck040/orgs","repos_url":"https://api.github.com/users/chickenchuck040/repos","events_url":"https://api.github.com/users/chickenchuck040/events{/privacy}","received_events_url":"https://api.github.com/users/chickenchuck040/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-03T14:47:22Z","updated_at":"2015-06-03T14:47:22Z","closed_at":null,"body":"1. What were you doing?\r\n\r\nMoving the printhead around. I set the movement step to 100 to move the XY around quickly, but then moved Z up, expecting the Z movement to still be on 10, but it moved up 100, as it should. This caused the Z axis to move up too high and hit the top of my printer.\r\n\r\n2. What did you expect to happen?\r\nI expected the Z to have its own movement step selector.\r\n\r\n3. What happened instead?\r\nThe Z axis used the same movement step as the XY, causing it to go too high\r\n\r\n4. Branch & Commit or Version of OctoPrint:\r\nVersion: 1.2.0-dev-864-gceb0e29 (devel branch)\r\n\r\n5. Printer model & used firmware incl. version\r\n   (if applicable - always include if unsure):\r\nTricolor mendel running an old version of Marlin.\r\n\r\n6. Browser and Version of Browser, Operating \r\n   System running Browser (if applicable - always \r\n   include if unsure):\r\nChrome, Firefox, Epiphany (Does not matter)\r\n\r\n7. Link to octoprint.log on gist.github.com or pastebin.com\r\n   (ALWAYS INCLUDE AND DO NOT TRUNCATE): N/A\r\n\r\n8. Link to contents of terminal tab or serial.log on \r\n   gist.github.com or pastebin.com (if applicable - always \r\n   include if unsure or reporting communication issues AND\r\n   DO NOT TRUNCATE): N/A\r\n\r\n9. Link to contents of Javascript console in the browser \r\n   on gist.github.com or pastebin.com or alternatively a\r\n   screenshot (if applicable - always include if unsure\r\n   or reporting UI issues): N/A\r\n\r\n10. Screenshot(s) showing the problem (if applicable - always\r\n    include if unsure or reporting UI issues): N/A\r\n\r\nI know that the build size can be set in Marlin, I just have not gotten to it yet, but I still think that this would be a useful feature."}}