{"action":"created","issue":{"url":"https://api.github.com/repos/jdtournier/mrtrix3/issues/29","labels_url":"https://api.github.com/repos/jdtournier/mrtrix3/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/jdtournier/mrtrix3/issues/29/comments","events_url":"https://api.github.com/repos/jdtournier/mrtrix3/issues/29/events","html_url":"https://github.com/jdtournier/mrtrix3/issues/29","id":33045703,"number":29,"title":"MRview: Lightbox mode","user":{"login":"Lestropie","id":5637955,"avatar_url":"https://avatars.githubusercontent.com/u/5637955?v=3","gravatar_id":"","url":"https://api.github.com/users/Lestropie","html_url":"https://github.com/Lestropie","followers_url":"https://api.github.com/users/Lestropie/followers","following_url":"https://api.github.com/users/Lestropie/following{/other_user}","gists_url":"https://api.github.com/users/Lestropie/gists{/gist_id}","starred_url":"https://api.github.com/users/Lestropie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Lestropie/subscriptions","organizations_url":"https://api.github.com/users/Lestropie/orgs","repos_url":"https://api.github.com/users/Lestropie/repos","events_url":"https://api.github.com/users/Lestropie/events{/privacy}","received_events_url":"https://api.github.com/users/Lestropie/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jdtournier/mrtrix3/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/jdtournier/mrtrix3/labels/gui","name":"gui","color":"eb6420"}],"state":"open","locked":false,"assignee":{"login":"draffelt","id":2948458,"avatar_url":"https://avatars.githubusercontent.com/u/2948458?v=3","gravatar_id":"","url":"https://api.github.com/users/draffelt","html_url":"https://github.com/draffelt","followers_url":"https://api.github.com/users/draffelt/followers","following_url":"https://api.github.com/users/draffelt/following{/other_user}","gists_url":"https://api.github.com/users/draffelt/gists{/gist_id}","starred_url":"https://api.github.com/users/draffelt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/draffelt/subscriptions","organizations_url":"https://api.github.com/users/draffelt/orgs","repos_url":"https://api.github.com/users/draffelt/repos","events_url":"https://api.github.com/users/draffelt/events{/privacy}","received_events_url":"https://api.github.com/users/draffelt/received_events","type":"User","site_admin":false},"milestone":null,"comments":7,"created_at":"2014-05-08T02:18:41Z","updated_at":"2015-02-24T10:13:04Z","closed_at":null,"body":"To show several slices at once of the same axis. Could be useful take a quick screen shot of results for meetings etc.\r\n\r\nFeatures could include:\r\n* User defined number of windows in x and y\r\n* User defined spacing between slices rendered in each window\r\n* User can still scroll through the image (ie, the image would therefore be seen to move * from one window to the next)"},"comment":{"url":"https://api.github.com/repos/jdtournier/mrtrix3/issues/comments/75730472","html_url":"https://github.com/jdtournier/mrtrix3/issues/29#issuecomment-75730472","issue_url":"https://api.github.com/repos/jdtournier/mrtrix3/issues/29","id":75730472,"user":{"login":"jdtournier","id":3221000,"avatar_url":"https://avatars.githubusercontent.com/u/3221000?v=3","gravatar_id":"","url":"https://api.github.com/users/jdtournier","html_url":"https://github.com/jdtournier","followers_url":"https://api.github.com/users/jdtournier/followers","following_url":"https://api.github.com/users/jdtournier/following{/other_user}","gists_url":"https://api.github.com/users/jdtournier/gists{/gist_id}","starred_url":"https://api.github.com/users/jdtournier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jdtournier/subscriptions","organizations_url":"https://api.github.com/users/jdtournier/orgs","repos_url":"https://api.github.com/users/jdtournier/repos","events_url":"https://api.github.com/users/jdtournier/events{/privacy}","received_events_url":"https://api.github.com/users/jdtournier/received_events","type":"User","site_admin":false},"created_at":"2015-02-24T10:13:04Z","updated_at":"2015-02-24T10:13:04Z","body":"> One option would be to have a dedicated 'mode-specific options' toolbar, that would contain only options that are applicable to specific view modes, e.g. clip planes for volume render, gridding for light box. Not sure if it actually solves any problems though.\r\n\r\nThat would be hard to achieve without sacrificing a fair bit of real estate in the top bar. There's quite a few of these controls, and some of them are multi-line - including Dave's suggested image list.\r\n\r\n> The view options can be manually dragged away from the other tool menus as it is, maybe it just needs some default parameter tweaking so that by default it will open on whichever side does not currently have any tools docked, and the user can always drag it onto the other tools to merge with them?\r\n\r\nYes, I think that's basically what we're talking about. From a coding perspective though, I think the best way to handle this it to have that particular sidebar _not_ be a Tool, since it would require a fair bit of custom handling to get right. I think it's core enough that it should be considered a part of the main UI, rather than an optional add-on (which really is what Tools should be). \r\n\r\n> We also discussed having the mode-specific options at the bottom of the the view toolbar disappear completely if that mode is not currently active.\r\n\r\nGood idea. Should be trivial to handle by calling `setVisible()` instead of `setEnabled()`. \r\n\r\n> If there's tool bar real estate, my preference would be to have a 'reverse order' tick box that would perform identically to a negative slice increment, and then limit the actual slice increment to be non-negative. I can see users being taken aback and reporting the current behaviour. It would also make it more consistent with other comparable controls e.g. slab thickness in the tractography tool.\r\n\r\nThat's why I raised the issue. The difference with the tractography slab width though is that a negative width is genuinely nonsense - there is no interpretation that makes sense. With the negative increments, it is well-defined, and very easy to understand when confronted with it. It's a bit surprising that it should allow this, but it shouldn't take long for users to see that it does make sense and that they might themselves find it useful someday. \r\n\r\nAnd generally, I'm in favour of allowing the broadest set of user input that we can reasonably interpret, since experience (mostly others', not just mine) shows that this allows the application to be used in ways we (the developers) hadn't envisaged. So I have a general bias towards allowing weird behaviours when it is entirely consistent (in terms of the code) with normal operation. \r\n"}}