On Jun 29, 2017, at 01:05 , Gerriet M. Denkmann wrote:
>
> and also the Container View has:
> Triggered Segues
> viedDidLoad TableViewController Embed
I have the same thing, so I don’t know what’s different.
> What I do not understand: Container View is a UIView, which does not have
> viedDi
> On 29 Jun 2017, at 12:13, Quincey Morris
> wrote:
>
> On Jun 28, 2017, at 22:02 , Gerriet M. Denkmann wrote:
>>
>> I had to do two more steps:
>>
>> 1. give the segue an identifier, like: “EmbedSegueToTableViewController”
>>
>> 2. in the UITableViewController which formerly did have a UIT
On Jun 28, 2017, at 22:02 , Gerriet M. Denkmann wrote:
>
> I had to do two more steps:
>
> 1. give the segue an identifier, like: “EmbedSegueToTableViewController”
>
> 2. in the UITableViewController which formerly did have a UITableView and now
> has the container view:
>
> - (void)viewDidLo
> On 29 Jun 2017, at 00:48, Quincey Morris
> wrote:
>
> On Jun 28, 2017, at 01:38 , Gerriet M. Denkmann wrote:
>>
>> I did just that.
>
> Not quite …
>
>> I have a Master View Controller Scene with a MasterViewController ←
>> UIViewController (which previously had a TableView, now has a UI
On Jun 28, 2017, at 01:38 , Gerriet M. Denkmann wrote:
>
> I did just that.
Not quite …
> I have a Master View Controller Scene with a MasterViewController ←
> UIViewController (which previously had a TableView, now has a UIView, called
> “Container View” ); it now also has:
> containerView →
> On 28 Jun 2017, at 14:37, Quincey Morris
> wrote:
>
> On Jun 28, 2017, at 00:21 , Gerriet M. Denkmann wrote:
>>
>> Ok, so I removed my TableView from the scene and tried to drag a
>> UITableViewController into its place.
>> But Xcode would not allow this.
>>
>> So: must a UITableViewContr
On Jun 28, 2017, at 00:21 , Gerriet M. Denkmann wrote:
>
> Ok, so I removed my TableView from the scene and tried to drag a
> UITableViewController into its place.
> But Xcode would not allow this.
>
> So: must a UITableViewController the only (or the top) thing in a scene?
> Or am I just doing
The particular initializer in use is
initWithCoder:
UITableView conforms to the NSCoding protocol. Hope this helps.
Damian
On Mar 12, 2013, at 11:09 AM, Koen van der Drift wrote:
> I'm playing around with a storyboard app on iOS. To test a TableView I
> created a UITableViewController sub
On Mar 12, 2013, at 12:32 PM, Ten Horses | Diederik Meijer
wrote:
> Have you tried moving those datasource codelines to viewDidLoad or
> viewWillAppear? It may be that when the view is instantiated from the
> storyboard init is not called?
>
I thought about that, and yes it works. I was hes
Have you tried moving those datasource codelines to viewDidLoad or
viewWillAppear? It may be that when the view is instantiated from the
storyboard init is not called?
Op 12 mrt. 2013, om 17:09 heeft Koen van der Drift
het volgende geschreven:
> I'm playing around with a storyboard app on i
On Wed, 03 Aug 2011 13:49:10 -0700, Jens Alfke said:
>As far as I can tell, UITableViewController only works when the table is the
>root of the nib
That's basically right. The docs are very clear on this: you must not use
UITableViewController unless the table view *is* the whole controlled vie
On Aug 3, 2011, at 3:49 PM, Jens Alfke wrote:
> I’ve got an iOS screen that incorporates a UITableView. This screen is run by
> a UIViewController subclass. I’d like to subclass UITableViewController
> instead, to get more table behaviors for free. The problem I’m running into
> is that the ta
Right, my mistakebut you get the idea.
On Jan 14, 2009, at 5:38 PM, Mohan Parthasarathy wrote:
As i mentioned, you can't return zero in
numberOfSectionsinTableView. You will get an exception
*** Terminating app due to uncaught exception
'NSInternalInconsistencyException', reason:
'
As i mentioned, you can't return zero in numberOfSectionsinTableView. You
will get an exception
*** Terminating app due to uncaught exception
'NSInternalInconsistencyException', reason: 'numberOfSectionsInTableView:
must return at least one section'
When the data is not ready you still return 1,
The way to invalidate data in the tableView when you free it would be
to reloadData. So, get rid of whatever you're getting rid of, build
your new, truncated list of items, and then call [tableView
reloadData] so you put only the data you've kept around in the table.
Also, if you're worried
Yes, that's what i meant. Just to confirm.. It is safe to assume that
numberOfSectionsInTableView will be first function called ? I am thinking of
this sequence..
1) The code receives low memory warning and frees up the data that the
tableView is currently displaying
2) CellForRowAtIndexPath is ca
I assume you meant numberOfSectionsInTableView:anyway, a good
strategy might be to just go ahead and return 0 initially, and then
whenever you have successfully pulled your data from the network, do
[tableView reloadData] and then you can return the appropriate numbers
at that time, sin
17 matches
Mail list logo
