<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"> The scrolling seems to work as designed (and as originally implemented<br>
in [1735] ). The bindings used are "SCROLLUP" (with help text, "Scroll<br>
image up," and default binding of 2) and "SCROLLDOWN" (with help text,<br>
"Scroll image down," and default binding of 8). When you use the SCROLLUP<br>
binding (2), the /image/ is moved up while the viewport remains fixed, so<br>
you see a portion of the image lower than the portion you were seeing.<br>
Similarly, when you use the SCROLLDOWN binding (8), the image is moved<br>
down while the viewport remains fixed, so you see a portion of the image<br>
higher than the portion you were seeing.<br>
<br>
If that's the case, then why doesn't SCROLLLEFT move the image left and<br>
SCROLLRight move the image right? They both move the viewport, as one<br>
would expect.<br>
<br>
</div></blockquote>
<br>
Well, I didn't write the code, so I couldn't tell you. All I can say for sure, though, is that this is how it's always worked.<br>
<br>
Perhaps a patch to the key description, then? As it is, it works like the keys on the numeric keypad on a keyboard indicate it should work, and changing which keys it uses is as simple as changing bindings in MythControls. So, unless we really change things/simplify things/make it more consistent with the rest of MythTV, I would argue we shouldn't change it since it's always been this way.</blockquote>
<div class="im"><br>Note that the current behaviour is already inconsistent with MythBrowser, which uses 8 for MOUSEDOWN and 2 for MOUSEUP, obviously intended for use with a remote control.<br><br>Changing the key descriptions doesn't seem like a good idea to me, since we'd end up with:<br>
<br> SCROLLUP - Scroll image down<br> SCROLLDOWN - Scroll image up<br><br>Or else SCROLLUP/SCROLLDOWN could be described as moving the viewport, which would differ from SCROLLLEFT/SCROLLRIGHT, which move the image.<br>
<br>Given the code, I can't explain this as anything but a bug. Just because it's a long standing bug doesn't mean it sholudn't be fixed. If there's anyone out there who likes it the way it is now, I'd be interested to hear why.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> My preference, however, would be to completely get rid of the SCROLLUP,<br>
SCROLLDOWN, SCROLLLEFT, and SCROLLRIGHT bindings used /only/ by<br>
MythGallery and change the plugin to use the global UP, DOWN, LEFT, and<br>
RIGHT bindings used everywhere else in Myth--where UP would scroll the<br>
viewport up (so you see a higher portion of the picture) and DOWN would<br>
scroll the viewport down (so you see a lower portion of the picture).<br>
Using the global directional keybindings works well for *both* keyboards<br>
and remotes (and would work fine for a remote without arrows if the user<br>
overrides the global bindings for the directional keys in the Gallery<br>
context to use numbers as now). I have a patch in the works that would<br>
allow users to add a new keybinding to a context using MythControls--<br>
effectively allowing users to override bindings in lower contexts with the<br>
GUI keybinding editor instead of direct DB editing.<br>
<br>
UP/LEFT are already used to move to the previous image, and DOWN/RIGHT<br>
move to the next image. Are you proposing changing the behaviour so that<br>
these keys behave differently during zooming, and not using the numeric<br>
keypad any more for scrolling?<br>
</blockquote>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ah, didn't realize that those were already used--though I think using the global PREVVIEW (Home) and NEXTVIEW (End) for previous and next image would be more consistent with the rest of Myth***. If we did that, then UP/DOWN/LEFT/RIGHT could be used to move the zoomed-in image up/down/left/right, and we wouldn't need to use the number-key hack we currently have--though I don't know what would work well for ROTRIGHT (3), ROTLEFT (1), RECENTER (5), ZOOMOUT (7), ZOOMIN (9), and FULLSIZE (0), so maybe it's not worth changing these.<br>
</blockquote><div><br>But my remote (Windows Media Center using Mythbuntu's default configuration) doesn't have any buttons mapped to Home or End. I'm guessing other remotes are similar, so I wouldn't like to see Home/End become the only way to move between images.<br>
<br>Really, I'm completely happy with the key bindings in MythGallery, except for the fact that this bug reverses the vertical scrolling directions.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I really don't know or use MythGallery, so as I mentioned, I'll let someone else who has more of a stake in the resolution decide.<br></blockquote></div><br>I'd be interested to hear from other people who use MythGallery. It could be that people just don't know about zooming and scrolling -- I discovered it just by mashing on my remote's keys to see whether anything interesting would happen. :-)<br>
<br>Regards,<br>Clayton<br>