Closed drallgood closed 10 years ago
Hi @drallgood I added about 40 elements to the first and second section each of the sample project, and the table scrolls just fine. Did you customize the control in any way?
I'm using these options:
AMOptionsEnableShadow : @(YES),
AMOptionsUseBorderedButton : @(borderedButton),
AMOptionsEnableGesture: @(NO),
AMOptionsBackground: backgroundColor,
AMOptionsSelectionBackground: [UIColor colorWithRed:.298 green:.572 blue:.815 alpha:1.0f],
AMOptionsHeaderFont: [UIFont fontWithName:@"AovelSans-Bold" size:20],
AMOptionsHeaderFontColor : [UIColor whiteColor],
AMOptionsCellFont : [UIFont fontWithName:@"AovelSans" size:18],
AMOptionsCellFontColor: [UIColor whiteColor],
AMOptionsCellBackground: backgroundColor,
AMOptionsCellBadgeFont : [UIFont fontWithName:@"AovelSans" size:15],
AMOptionsHeaderFont : [UIFont systemFontOfSize:14]
The menu items are added to the controller via the setMenuItems: method. Each menu item is added to the menuItems array with the following code:
NSMutableDictionary* item = [[NSMutableDictionary alloc] init];
item[kSOController] = controller;
item[kSOViewTitle] = controller.roomName;
item[kSOViewIcon] = @"";
item[kSOViewTag] = @(controller.roomNumber);
[menuItems[0][kSOSection] addObject:item];
Hi I tried with your options, and still can't reproduce the issue. Can you reproduce it in the sample project?
To be honest: No. I can't either. Just tried it and it worked just fine... which is weird because I don't think I did anything special.
I copied all the code that has to do with SlideOutNavigation to the sample app delegate and even tried to reproduce the delayed (asynchronous) update of the list.
Any idea how to find out what's going on?
I managed to reproduce it after all! It's working fine on the iPhone but not on the iPad.
Here's the project: https://dl.dropboxusercontent.com/u/17133427/SlideOutSample.zip
Huh, funny thing is, in portrait orientation it works fine. So I guess the culprit is the orientation handling. I'll look into it.
Commit 39741e8 should fix the issue.
Now it's completely broken ;)
Now that's fun. Removing the code that I added yesterday, the issue persists. It's probably due to the last pull request that I merged, which added quite a bit of code. I have to figure out what's causing this. I'll keep you posted.
Haha... Yeah. I figured that out, too. I'll dig around a little bit, too, and let you know when I find something that might help.
Ok, found the culprit.
if([dict[kSOViewTag] integerValue] == self.currentTag) {
[self hideSideMenu];
return;
}
You need to use tags (greater than 0) or the first call to the VC selector will do nothing. I'll push a new version later, I guess I'll just remove those lines, since they break compatibility pretty bad.
Checkout commit e598aa4
hmm.. That didn't do it. It's still not showing the first controller
Sorry. My bad. It did fix it. Somehow I just thought I had pulled your changes and apparently I didn't.
Thanks for your time!!!
Glad I could help. :beer:
For testing purposes, I've added 30 elements to the first section (which is usually filled with the users data => might vary in size) and 2 to a second one.
Now I can't scroll all the way down to the second section.
Any idea why this is happening?