4 replies to this topic

[Seth Vanderdrift]

Was not sure which forum to put this in.

 

I'm using STV 5.1.3 (Checked the framework headers before posting), Xcode 7.1 (7B91b)

 

I'm making the table view models via code.  I have a Salesforce data class object, I'm making the class def and sections as below.  I'm manually generating the sections for one object with [TableViewModel generateSectionsForObject:withDefinition:]

 

For what it's worth, its in a detail view of at UISplitTableViewController.

 

Class definition:

- (void) configStudentInfo
{      
    SCClassDefinition *classDef = [SCClassDefinition definitionWithClass:[M2ClientStudentSObjectData class] propertyNamesString:@":(fieldClientExtID__c);Basics:(fieldFullName__c,fieldFirstName__c,fieldMiddleName__c,fieldLastName__c,fieldDOB__c,fieldGender__c)"];
    
    classDef.requireEditingModeToEditPropertyValues = YES;
    
    SCPropertyDefinition *studentIDDef = [classDef propertyDefinitionWithName:@"fieldClientExtID__c"];
    studentIDDef.title = @"Student ID";
    
    
    SCPropertyDefinition *fullNameDef = [classDef propertyDefinitionWithName:@"fieldFullName__c"];
    fullNameDef.title = @"Name";
    fullNameDef.existsInEditingMode = NO;
    fullNameDef.type = SCPropertyTypeLabel;
    fullNameDef.cellActions.didLayoutSubviews = ^(SCTableViewCell *cell, NSIndexPath *indexPath)
    {
        SCLabelCell *labelCell = (SCLabelCell *)cell;
        labelCell.label.textAlignment = NSTextAlignmentLeft;
    };
    
    
    SCPropertyDefinition *firstNameDef = [classDef propertyDefinitionWithName:@"fieldFirstName__c"];
    firstNameDef.title = @"First";
    firstNameDef.existsInEditingMode = YES;
    firstNameDef.existsInNormalMode = NO;
    
    SCPropertyDefinition *middleNameDef = [classDef propertyDefinitionWithName:@"fieldMiddleName__c"];
    middleNameDef.title = @"Middle";
    middleNameDef.existsInEditingMode = YES;
    middleNameDef.existsInNormalMode = NO;
    
    SCPropertyDefinition *lastNameDef = [classDef propertyDefinitionWithName:@"fieldLastName__c"];
    lastNameDef.title = @"Last";
    lastNameDef.existsInEditingMode = YES;
    lastNameDef.existsInNormalMode = NO;
   
    
    SCPropertyDefinition *dobDef = [classDef propertyDefinitionWithName:@"fieldDOB__c"];
    dobDef.title = @"DOB";
    dobDef.existsInEditingMode = YES;
    dobDef.existsInNormalMode = YES;

    SCPropertyDefinition *genderDef = [classDef propertyDefinitionWithName:@"fieldGender__c"];
    genderDef.title = @"Gender";
    genderDef.existsInEditingMode = YES;
    genderDef.existsInNormalMode = YES;
    
    
    self.tableViewModel = [SCTableViewModel modelWithTableView:self.tableView];
    
    [self.tableViewModel generateSectionsForObject:self.studentObject withDefinition:classDef];
    
}

 

On both an iPad 3, and iPod Touch 6, in edit mode, DOB and Gender fields are under the keyboard. You can edit them fine, just can't see them.  Also can't scroll it up manually either.  Won't scroll high enough to get above the keyboard. Also, trying to scroll up closes the keyboard.

 

At this point, not sure how to debug it.  There's not much more code when whats above.  

 

Thanks

Seth

 

 

[Seth Vanderdrift]

Ok, so I added 

    self.tableViewModel.cellActions.didBecomeFirstResponder = ^(SCTableViewCell *cell,
                                                                NSIndexPath *indexPath) {
        NSLog(@"Cell at indexPath:%@ has become the first responder.", indexPath);
        [self.tableView scrollToRowAtIndexPath:indexPath atScrollPosition:UITableViewScrollPositionMiddle animated:YES];
    };

 

It still won't scroll UNLESS I add additional fields below to make the tableView longer.  Then it will scroll to Gender, but not the  fields I added below that.  So the tableView/scrollview content insets aren't expanding to accommodate the keyboard (at least that the way I've done for keyboard management with non STV views)

[Tarek]

Hi Seth,

 

Is this an SCTableViewController or SCViewController? If it's an SCTableViewController, then the scrolling issues probably have very little to do with STV itself.

[Seth Vanderdrift]

Tarek,

 

Ok, I figured it out.  I'm presume it's documented, but I had some debug code in the SCTableViewController subclass, which used viewWillAppear: to log the object.

 

When I added the commented out [super viewWillAppear:animated], the scrolling started working as expected.

 

- (void) viewWillAppear:(BOOL)animated
{
//    [super viewWillAppear:animated];
    SCTableViewSection *firstSection = [self.tableViewModel sectionAtIndex:0];
    
    NSLog(@" -- DetailView %@", firstSection.boundObject);
    
}

 

So in general all the viewWill... viewDid....  methods should call super.(??)

 

Thanks,

Seth

[Tarek]

Yes of course, it's essential to the STV framework that these methods call super.