New answers tagged listview
Ask your users :) It's hard to give advice or any facts without knowing the context of your application. Depending on their mental model, they may want to flick through as fast as possible (a specific picture is their target) or just casually flick through (more like entertainment). If you can't do user testing: Measure their flicking speed and "read" the ...
You have a number of options... Widen the listbox and add more columns to it, facilitating more informed item selection. Enlarge the font size to fit the screen space available, easing eye strain. Add a third column to the full screen view and add useful information such as field-level instructions, non-editable fields like record #s and creation dates, ...
Seems like that the only thing you can do here is expand the width of the text input fields to 100% and put the buttons in the lower right corner. You simply don't have enough material to make a full screen look good. Or just disable full screen on that view.
Best practice may not apply to a location There may be enough examples (Google Analytics and Podio are two more) that place toggles like this to the top and right of the content to say that it's a conventional location, but I'd argue that the location of controls like this should depend on the specific application and user goals. Examine your motivation ...
If you're wanting to just follow the norm then top right is pretty typical. I don't recall any specific black and white conventions for this specific thing, but it's typically a good idea to go along the lines of what other large products do. As Devin mentioned, Google Drive keep their grid/row toggle in the top right which is consistent with where Windows ...
I don't know of any best practice standard. There certainly seems to be a trend for top right, Google Drive makes use of this using a single toggle button.
Top 50 recent answers are included