Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This should actually be fairly easy to do. </p> <ol> <li>First, you need to set up the existing view controller (the one associated with the view where you want to add your button) with an IBOutlet for your new button. So you add something like: <pre> @property (nonatomic, retain) IBOutlet UIButton *myFourthButton; </pre></li> <li><p>Next, create the nib file with Interface Builder. Start with an empty IB file and add your button to it. You also need to set the File's Owner to be an instance of the view controller class. Then connect the File Owner's myFourthButton outlet to your new button. Save the IB file.</p></li> <li><p>Now you need some way to load this NIB file when the view controller is created. I would suggest doing this in the view controller's viewDidLoad: method by calling:</p> <pre> [[NSBundle mainBundle] loadNibNamed:@"yourNibFile" owner:self options:nil]; </pre></li> <li><p>The button from the NIB file should now be connected to your myFourthButton outlet, now you just need to add it to the view and position it. Below I add it to the view controllers main view. However, there may be a subview that you should add it to instead (depends on how the original view is set up). Again, I would put this code in viewDidLoad: after all of the existing code to set up the view programmatically (or in another method if that code is elsewhere).</p> <pre> [self.view addSubview:myFourthButton]; CGRect frame = myFourthButton.frame; frame.origin.x = 100; frame.origin.y = 100; myFourthButton.frame = frame; </pre> <p>When you need your button to actually respond to a tap event, you can connect it to your view controller using an IBAction and Interface Builder just as you would expect.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POAdding view created in Interface Builder to Progmatically created view - can it be done?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTim Isganitis
    1. USTim Isganitis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAdding view created in Interface Builder to Progmatically created view - can it be done?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis sounds like it makes sense to me. So essentially I'm keeping the current .h and .m file and using a NIB to 'cheat' making buttons? When I want to add an IBAction to the button do I just end up doing this exactly the same as if I'd added a new class with .xib? I'll give this a go tomorrow evening (I'm working on a big project right now and I've had my fill of Xcode for the night!) I'll mark up as an answer as appropriate if it works for me :-)
      singulars
      1. PO
      1. USDavid26th
    2. COCorrect, you are using the existing .h/.m files for the view controller. This isn't really "cheating," there are plenty of instances where it makes sense to mix interface elements created programmatically and via IB (table view cells are one good example). Basically, instead of instantiating and configuring the UIButton yourself, you are letting the nib loader do that work for you. At the end of the day, I think it makes sense to work with what you are most comfortable with.
      singulars
      1. PO
      1. USTim Isganitis
    3. COIn terms of adding an action, you would first declare the IBAction in the view controller's .h/.m files, then drag a connection from the UIButton to the File's Owner (the view controller). Good luck!
      singulars
      1. PO
      1. USTim Isganitis
 

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