Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am curious why you are doing this in story board. IF you need Xib's this custom perhaps you want to create an individual "test" project to work out just the view. I would highly recommend that from a software engineering standpoint, but then again I recommend against story boarding to begin with to my students for any production level project, its good for somethings but it has so many down falls as an individual developer and exponentially more down falls as a team development tool. Well end my self righteous rant.</p> <p>There are three ways I can think of to solve your problem if I understand it correctly. The problem:</p> <ul> <li>I have a view with the lowest layer being a scroll view, I have two subviews on top of it that are UIButtons. </li> <li>The buttons will vary in size due to content(assuming text/font changes, and possible pictures?).</li> <li>I want the buttons to appear next to each other in a consistent manner even though their size will vary.</li> <li>I want to support multiple orientations and possible multiple idioms.</li> </ul> <p>Solution Suggestions: 1.Due to the complex nature of the problem my first suggestion is going to probably seem a little less then fun. Work out the view programatically, using relative geometric math you can solve all of your issues, it may seem daunting but it will really be the cleanest and easiest way I think by creating a custom view controller that as info updates the controller will manage the view to display appropriately, also the advantage of this is if you are really good at relative geometry your code will work across idioms.</p> <ol> <li><p>Work it out with springs and struts, then test it in every way you can think of but this wont be as good as a math proof for geometry based approaches. Why you may ask, because a higher level solution does not guarantee you control. But emphasize relative resizing and positioning as you set this up.</p></li> <li><p>This is wasteful unnecessary and will slow performance a lot, but I have had it turned in by a senior in computer science.(Poor guy never got more then 2/15 of the subjective points)</p></li> </ol> <p>Create a view for just about every situation and have an overly complex controller switch between them. The performance costs on this are gigantic and the potential for someone finding a means to a screen that is not consistent is VERY likely.</p>
    singulars
    1. This table or related slice is empty.
    1. POButton positioning in relation to each other
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USThat Guy
    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. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat *are* you talking about? This is a very simple problem to solve with Apple's new layout constraint system.
      singulars
      1. PO
      1. USrdelmar
    2. COTHanks a lot for the elaborate answer. It ended up being as simple as making horizontal spacing on the buttons.
      singulars
      1. PO
      1. USHolger Edward Wardlow Sindbæk
    3. COSimple, yes for "most" uses that would be the recommended way of doing this. However, the question posted was with the idea of variable content in the bars. When dealing with dynamic content the struts and strings can not always be counted on, especially if say the content or its format exceeds the screen limits. If my buttons dynamic content was always between 1- 9 characters I would strut spring this and never think about it again. However if I my dynamic content is 1-? I do not want "?" biting me causing for a bad app experience.
      singulars
      1. PO
      1. USThat Guy
 

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