Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Thanks, Adam. I am indeed doing this because the keyboard is causing text to be hidden behind and I'll get to that in a sec. </p> <p>What you suggest with respect to the UIImageView is exactly what I was planning but in reverse. I wanted the 300 height textView, with the lower portion covered by the keyboard to then have a UIImageView sliver just above the keyboard of the rounded bottom portion of the grouped tableView that the textView is in. (The textView is in a tableViewCell in a single section/single cell tableView.) Adding the sliver of an image would make the larger textView, covered by the keyboard look like a small textView when the keyboard is present, and when dismissed and image removed/restored, textView would be larger, to allow the user to read all of the notes they've entered. </p> <p>With the solution that I was looking for, scrolling to stop anywhere within the textView, the smaller textView would start scrolling at the correct place, just above the sliver image which is just above the keyboard. </p> <p>Now to the "just size the textView" suggestion. Easier said than done. Because the textView is in a grouped tableView, with keyboard present, I created a smaller textView in a tableViewCell with nicely rounded corners, but when I size the textView larger, only the center portion extends (about 90% of the rounded rectangle in the center), not the rounded corners on the sides (5% of the width on each side remains the same). Next thought: Can't extend the textView without increasing the height of the cell so...</p> <p>...the solution is therefore to resize the cell; but that involves a reloadData or begin/end updates which only work with a cell or section insert. I was then thinking of just adding a new section so the reloadData would work, but then I'd have to turn off scrolling on the scrollView so the new section would never be seen and I'm having trouble with that despite trying every permutation of scrollEnabled=NO (on tableView, textView, scrollView, parent).</p> <p>And finally, shifting the entire screen upward works beautifully but with a large textView, I'd then have to prevent typing in the non-visible upper portion when scrolled upward, so that was rejected. Although it just occurred to me that with the CGRect's size.height equally reduced, typing may not occur in the non-visible portion - but I still lose the rounded top of the grouped tableView so cosmetically it could look better - still rejected.</p> <p>So, that's my story and that's been my day. Any help from anyone would be greatly appreciated. </p> <p>I think my best bet is adding the "fake" section to the tableView and setting it to hidden, so I can get the new cell height to kick in. but I still have to turn off tableView scrolling or scrollView scrolling so a scroll in the textView doesn't unnecessarily move the entire screen since the space for the hidden section would probably be there and therefore scrollable.</p>
    singulars
    1. This table or related slice is empty.
    1. POUITextView Scrolling - Artificial Limit
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt Winters
    1. USMatt Winters
    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. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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