Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>UITableView</em> only supports one column. This was an iOS design decision taken due to the much smaller nature of the original iPhone and then iPad screens.</p> <p>If you wanted to have more than one columns then you'd have to create your own class that perhaps includes multiple <em>UITableViews</em>, or your own custom <em>UIControl</em>. I think if you were to attempt this you'd find yourself fighting the framework and you'd be misunderstanding the nature of apps for these platforms.</p> <p>Perhaps you should consider using a <em>UINavigationController</em>, <em>UITabBarController</em>, or some other means of navigating the app, with multiple <em>UITableViews</em> in order to present information to the user?</p> <p>Hope this helps.</p> <p><strong>Response to Edit:</strong></p> <p>In a word... no.</p> <p>In more than a word, yes - you just can't achieve this using the traditional and reccomended <em>UITableView</em>. As I said before, consider rearranging your data so as you only display a certain amount at a time. For example, you could have one <em>UITableView</em> that displays a list of all the batch codes, and when the user taps on one of the cells, a second <em>UITableView</em> could be transitioned to (using a <em>UINavigationController</em>) that displays the more detailed info of 'beginning control #', 'beginning sequence #' etc. etc. This sort of user interface is what you see all over apps on the iOS platform.</p> <p>Alternatively, you could create a custom <em>UIView</em> or <em>UIControl</em> subclass that displays the information exactly you'd like it, perhaps by overriding the <code>drawRect:</code> method. But imagine how the example you've given above would look like on an iPhone in portrait mode... Not very good and not very user friendly. You could perhaps also use an image for the table, and allow the user to scroll over the image as they would when zoomed in the Photos app. You could embed custom controls into a scroll view to achieve this. But again, the user interface probably wouldn't meet the standards for ease of use, simplicity and clarity that users expect from iOS apps. In my opinion, the best solution here is to figure out a way to logically split your data across multiple <em>UITableViews</em>. Try taking a good look at what some of the other apps out there do and how they manage to really effectively get around the small space problem. :)</p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload