Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFString sizeWithAttributes:]: unrecognized selector sent to instance 0x9c74440'
*** First throw call stack:
(0x2f42012 0x2d67e7e 0x2fcd4bd 0x2f31bbc 0x2f3194e 0x280dd0 0x2799fa 0x1b838fb 0x1b839cf 0x1b6c1bb 0x1b6a872 0x1b755d4 0x1b781c4 0x1b78546 0x278d5e 0xaaad 0x1baa1c7 0x1baa232 0x1bb5c25 0x1db53a3 0x1bb2ee3 0x1bb3167 0x1bb31a7 0x2164dd 0x979a6 0x9876a 0x26385e 0x2644b1 0x365653f 0x3668014 0x36587d5 0x2ee8af5 0x2ee7f44 0x2ee7e1b 0x3b627e3 0x3b62668 0x1ac8ffc 0x257d 0x24e5 0x1)
libc++abi.dylib: terminate called throwing an exception

Because following code is wrong (__IPHONE_7_0 is defined, but it doesn't mean that iOS7 is used!)

ifdef __IPHONE_7_0

    CGSize fontSize = [text sizeWithAttributes: @{NSFontAttributeName: self.options[AMOptionsCellBadgeFont]}];

else

    CGSize fontSize = [text sizeWithFont:self.options[AMOptionsCellBadgeFont]];

endif

I'm using some startup view controller and your sliding controller as second screen. To avoid double navigation bar, i'm hiding original bar, with Back button and use sliding navigation bar menu instead. But i need to have possibility to return back to original (start) controller from some inner contentview controller.

How to do it?

Steps to reproduce:

1. Run SlideoutStroryboardSample
2. Try to click on rectange area marked as red (see screenshot)

Actual: clicking far from Side button on UINavigationBar fires action, even though clicking on View area which doesn't know about button will fire click action too.
Expected: ~ only yellow area should accept clicks

is there anyfix where slidout looks the same in ios 6 and ios 7
in ios6 it looks blue whereas in ios 7 it is grey

Hi.
I've gotten a few weird crash reports from a user that seem to indicate a crash in AMSlideTableCell.m line 33.
Looks like the options array is garbage/missing (NSMutableRLEArray objectAtIndex:effectiveRange:: Out of bounds).
Any idea what that might be?
iOS 7 issue?

Due to new behavior iOS 7 the following line AMSlideoutNavigationController.m adds extra padding.

self.contentController.navigationBar.translucent = YES;

/*
New behavior on iOS 7.
Default is YES.
You may force an opaque background by setting the property to NO.
If the navigation bar has a custom background image, the default is inferred
from the alpha values of the image—YES if it has any pixel with alpha < 1.0
If you send setTranslucent:YES to a bar with an opaque custom background image
it will apply a system opacity less than 1.0 to the image.
If you send setTranslucent:NO to a bar with a translucent custom background image
it will provide an opaque background for the image using the bar's barTintColor if defined, or black
for UIBarStyleBlack or white for UIBarStyleDefault if barTintColor is nil.
*/

see snapshots below

https://www.dropbox.com/s/zdw3lgqt8rz5hrw/Screen%20Shot%202013-07-04%20at%20%E4%B8%8B%E5%8D%885.41.47.png

I was going to hack the code to do what these options appear to do. They don't currently appear in the documentation (README), however.

Hi @andreamazz!
Thanks for simple and amazing framework.

I want to propose such enhancements:
1.Add property to specify navigation bar style (currently it's blue by default) or more configurable (I see tranding apps don't use default Apple gloss in navigation bar)
2.Set navigation bar title by default with selected cell title from table view:

[self.slideoutController addViewControllerToLastSection:controller
      tagged:1
      withTitle:@"First View" // this title is used for cell and in navigation bar title (currently it's empty)
       andIcon:@"icon1.png"];  

3.Remove code that sets barButton to UIBarButtonItemStyleDone. IMHO: it looks not bad for default blue style but with other cases (black or probably red) it looks ugly. Path, Facebook and others don't emphasize the status of this button.
4.Adjust kSlideValue according to this UI recomendations. I've tried ~270 and it looks good (not sure because code at home 😄 )

Hi, andreamazz

I want to add some customized cell , how to do it? It will change back to default style, even though I return my customized cell on my AMSlideOutNavigationController instance .

I have 10 items,and 3 sections.
When I scroll to bottom,and click last item, first section head ,it's postion is error.

Is it possible in this code to send a message to one of the view controllers that it should stop displaying iAds before it is slid aside, and that it can start displaying them again when it is slid back?

Hi,
Is it possible to add second bar button to the right side.Using Push or Modal to open another ViewController.Example Search button.
Thank you

I've been loading my slideOutNavigation class after the user passes a login prompt. I replace the rootviewcontroller inside a UIView transitionWithView animation block.

Works well except the navigation bar at the top drops 20 points immediately after the transition completes, only on iOS 7.0.

From my digging around it seems right now that most likely I'm facing the same issue described here: http://stackoverflow.com/questions/14795645/uinavigationbar-jumps-20pixels-during-transitionfromviewcontroller

I have attempted the suggested resolution (it didn't work) but maybe I did it wrong. I can't get a handle on how SlideOutNav is using the navigation bar.

Specifically I don't understand the following: (AMSlideOutNavigationController.h)
@Property (nonatomic, assign) Class navigationBarClass;

and also in the corresponding .m file
self.contentController = [[self.navigationControllerClass alloc] initWithNavigationBarClass:self.navigationBarClass toolbarClass:self.navigationToolbarClass];

It looks to me like maybe AMSlideOutNavigationController is subclassing uinavigationbar in an indirect way. The superclass is UIViewController, and no UINavigationBarDelegate protocol is being declared, so perhaps this is a trick to get around single-inheritance?

I tried adding - (BOOL)wantsFullScreenLayout but there was no change.

Any suggestions?

There's a bug in AMSlideOutNavigationController.m in line 106:
The method call isn't forwarded to addViewController:tagged:withTitle:andIcon:toSection:beforeChange:onCompletition: but to addViewControllerToLastSection:tagged:withTitle:andIcon:beforeChange:

I may be doing something wrong but i think the AMOptionsCellBackground option with clearColor to get transparent cells does not work anymore. I have a white background.
Maybe the cells are set to "opaque".
Thank you

I have a weird bug. Sometimes i have a gap on the top of the views and sometimes not...

You can compare these images :
https://dl.dropboxusercontent.com/s/xrtyrzi8wxscxiv/2013-09-10%20at%2014.33.png

and

https://dl.dropboxusercontent.com/s/eas6jinu7ip866t/2013-09-10%20at%2014.34.png

It happens sometimes when i try to slide out or slide in the view. Sometimes not...

Could it be a problem with status bar being hidden sometimes ?

Thank you in advance

I don't know if this is something useful or maybe there is another already done way to get it, but i saw when i add the tableview to the navigation controller, there is the offsetY 20 pixels, but when you scroll up you see how the tableview "cuts" in those 20 pixels, so i changed it to 0 and added this to the code:

self.tableView.contentInset = UIEdgeInsetsMake(20, 0, 0, 0);

so now when i scroll up i see the table cell behind the status bar info and not cut.

it would be great to add that functionality as an option or id there is a "correct" way to do this behavior with the current version of this class please tell me :D

thanks for sharing this amazing work.

Hi, I was wondering if it was possible to disable AMOptionsEnableGesture just in one view?

The issue is that UIPanGestureRecognizer interferes with swipe to delete on a UITableViewController. Basically swipe to delete no longer works.

Or perhaps you know a workaround so that AMOptionsEnableGesture works with swipe to delete on a UITableViewController.

I see now how to disable all gestures but I want to disable them only for 'child' controllers, i.e. support iOS 7 built-in gestures for "Back"

I want a bar button with UIBarButtonItemStylePlain style. According to these lines, it is possible by setting AMOptionsUseBorderedButton to @(YES)

if ([self.options[AMOptionsUseBorderedButton] boolValue]) {
    self.barButton = [[UIBarButtonItem alloc] initWithImage:self.options[AMOptionsButtonIcon]
                                                      style:UIBarButtonItemStylePlain
                                                     target:self
                                                     action:@selector(toggleMenu)];

    accessibilityObject = self.barButton;

}

However, there is also UIBarButtonItemStyleBordered style that actually conflicts with the term.

Hi @andreamazz

I see that swipe gesture can't be disabled (for example I want to show side view only by button click)

Example of usecase:

1. Open your SlideOutSample (not storyboard).
2. Select 'Second View' from 'First Section'
3. Click on the latest button - 'Set badge for Second View, Second Section' which loads child view

On this child view you can show side view by swiping on UINavigationBar or entire view.

In some cases I want to disable.

Just added [self.slideoutController setBadgeValue:@"1" forTag:2];
to the AMAppDelegate within SlideoutStoryboardSample, but doesn't see any badge text.

I added this to the end of AMSlideOutNavigationController.m :

  - (BOOL)prefersStatusBarHidden  {  return YES; }

That removes the status bar in the children views but not in the slideout menu.

Do you know a way to remove it everywhere ?

Hello,

I'm using this framework and have noticed a lot of users miss the icon because they try to touch it in the upper left corner. So they touch a few times and finally manage to target it on the third try. This feels like a usability fail.

This is actually a well-known user interface / usability phenomenon also known as Fitts' Law; that people tend to navigate on screens and user interfaces relative to corners and edges of the screen. This is for example why you can open the apple menu by clicking in the upper left corner of your screen. Also, the back button in all iOS applications is reachable by clicking in the corner.

Sorry if that motivation is a bit too long. :)

I've been looking into how to extend the hit rect while keeping the menu icon intact. Maybe by changing the padding of the containerview for this icon somehow? Any ideas?

Thanks for a great framework!

I didn't find a way to add separator lines between menu entries, I think it would be a nice feature to have for the clarity of the menu. I'm aware of the sections feature, but I don't need to display a text between my groups of entries.

Some new settings would be needed such as :

• AMOptionsSeparatorLineWidth: @(float), Width of the separator lines in percent. Defaults to 90
• AMOptionsSeparatorLineHeight: @(float), Height of the separator lines in pixels. Defaults to 1
• AMOptionsSeparatorLineColor: UIColor, Color of the separator lines. Defaults to [UIColor whiteColor]
• AMOptionsSeparatorLinePadding: @(float), Amount of vertical padding for the separator lines in pixels. Defaults to 0

Hello, i just noticed the table view loses its selected cell when you are scrolling the table, how can i fix that?

thanks.

I'd like to be able to choose which controller to display by default, not the first in the menu. I've got a menu where the first entry is the search page and I don't want it to be displayed by default.

Hi, do you notice that UI becames less flud when inserted in this controller on iPhone4?
I don't know yet if this is specific to my app. I have a couple of table view controllers, controller by the sldeout nav controller and I notice that iPhone has hard times when doing animations. This is not present on iPad and also emulator works just fine

I added this method in AMSlideOutNavigationController.m to make it work :

-(BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)toInterfaceOrientation
{
    return YES;
}

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?

I have this code in AppDelegate:

    self.rootNavController = self.slideoutController.contentController; 
    self.rootNavController.navigationBar.barStyle = UIBarStyleBlackTranslucent;

It works. Then I have the following view configuration:
0: Table View (highly customized). No problem with that
1: Conventional static UIView. No problem also here
2: Just a standard Table View with a couple of rows. Here is an issue. When you switch between this view and other view, every time you turn back here, you notice your table is shifted down by the offset = top bar height (I suppose). If the nav bar is not transcluent, this problem is not present.

I think there is something with arithmetics, because when the bar is transcluent, the content goes also under it

Up until your commit today, it was possible to directly manipulate the menuItems array and remove certain entries or clear them out entirely.

Do you think it would be possible to get this functionality back somehow?

I was using it to dynamically add controllers based on data I get from a server.

After implementing the slide out controller, tapping the status bar no longer scrolls to top.

Hi,
Great control :-)
Would it be easy to add a slide animation for the menu ?
Thank you !

Hello,

When i run the menu in landscape mode i get this:

http://cl.ly/image/0f2V3R0y3W0U

but if in that same run i change the orientation it gets fixed, this only happens when i run the app in landscape, if i run it the first time in portrait, it shows the correct size of the table.

Thanks

In the project I'm working on, we chose to go with a scalable image format with a library that returns a UIImage from our proprietary format asset. Would it be valuable to this project to use UIImage objects instead of strings as the icon images? Let me know if that doesn't make sense.

This class is not using the view controller containment methods introduced in iOS 5. As such, this class will not handle certain things properly, one of them being rotation.

For menus that are small enough to be entirely displayed on the screen it would be nice to have an option to disable scrolling when dragging them, else they are bouncing.

Could be by default, probably best since it doesn't make sense to be able to bounce in this case, or with an option :

• AMOptionsMenuScrolling // @(BOOL), Enables scrolling for the menu. Defaults to @yES

Because I want a very customized back button, I've hidden the default button and replaced it with an overriden leftbutton. Thus, I'm left to code the navigation 'back' function manually. I followed this article: http://beageek.biz/how-to-add-custom-code-navigation-controller-back-button-xcode-ios/

The question is that when I try to pop the view controller, using the navigation controller in the AMSlideOut, the view doesn't change. I'm guessing that this is a side effect of the root view being the AMSlideOut and not directly a UINavigationController. Is this true?

From reading the code, - (void)loadView appears responsible for updating the contentViewController (which, in reality, is the navigation controller), but when I call it, I get a dark/lack screen.

Here is my code:

-(void)back{
    NSLog(@"You touched me!");
    AppDelegate *delegate = (AppDelegate *)[[UIApplication sharedApplication] delegate];
    [delegate.slideoutController.navigationController popViewControllerAnimated:TRUE];
    [delegate.slideoutController loadView];
}

The expected behavior, if I were working with a navigation controller directly, is that the present view controller would be dismissed. To test this, I used this code, slightly modified, in a new 'Master-Detail Application':

- (id)initWithNibName:(NSString *)nibNameOrNil bundle:(NSBundle *)nibBundleOrNil
{
    self = [super initWithNibName:nibNameOrNil bundle:nibBundleOrNil];
    if (self) {
        self.title = NSLocalizedString(@"Detail", @"Detail");
        UIImage *back_img = [UIImage imageWithPDFNamed:@"navigation_back.pdf" atHeight:40];

        UIButton *back_view = [UIButton buttonWithType:UIButtonTypeCustom];
        [back_view setFrame:CGRectMake(0,0, 40, 40)];
        [back_view setBackgroundImage:back_img forState:UIControlStateNormal];
        [back_view addTarget:self action:@selector(back) forControlEvents:UIControlEventTouchUpInside];

        UIBarButtonItem *back_btn = [[UIBarButtonItem alloc]initWithCustomView:back_view];
        self.navigationItem.hidesBackButton = YES;
        self.navigationItem.leftBarButtonItem = back_btn;
    }
    return self;
}

-(void)back{
    NSLog(@"You touched me!");
    AppDelegate *delegate = (AppDelegate *)[[UIApplication sharedApplication] delegate];
    [delegate.navigationController popViewControllerAnimated:TRUE];
}

The result was as expected. The last view controller was popped from the stack and I was navigated back to the previous view.

I am willing to implement the code to make this behavior available, but I am uncertain which direction you'd like to take. I would propose making AMSlideOut an overridden UINavigationController instead of a UIViewController and implement the appropriate methods, interacting directly with the navigation stack. I've never done so, so it may be easier for someone else, even yourself.

@andreamazz I have another new idea 😄

What about adding item just for some action without loading any view.
For example:

[self.slideoutController addItemToSection:1
    withTitle:@"Item just with action"
      andIcon:@"icon1.png"
    andAction:^{
        UIAlertView *alert = [[[UIAlertView alloc] initWithTitle:@"Some action"
                                                         message:@"Some message." 
                                                        delegate:nil 
                                               cancelButtonTitle:@"OK"
                                               otherButtonTitles:nil] show];
}];

Hi @andreamazz again 😄

I've caught very interesting issue.

I've created a simple project based on one of your examples. You can download it here

Description of example
1.Settings can be shown only by clicking on button:

[self.slideoutController setSlideoutOptions:@{AMOptionsEnableGesture : @(NO)}];

2.There is 'First View' that has UITableView and 'Child' bar button to push similar view. As swipe gesture is disabled you can't open settings from 'Child View'.

If you look at my video on youtube you can see that during some panic clicking it's possible to have loaded 'Child View' in slided out view. Maybe it sounds not clear but hope video will explains better.

After that this slided out view can catch events and you can return to parent view and make some actions on it.

As I see AMSlideOutNavigationController during showing side menu just move content for some value and put transparent view on it. (Correct me if I'm wrong)

1. First of all what can you say about this video?
2. What about not moving view but making screenshot and moving screenshot to avoid such side effects when slided out view can catch events?

I've implemented a custom slider.
When using it standalone it works fine, but when I try to use it in a subview of AMSlideOutNavigationController it reacts choppy. This happens even if I've disabled the gestures for the navigation controller.
This is (probably) due to the fact that disabling the gestures doesn't actually do very much. The gesture handlers are still registered, they just aren't handling the gestures anymore.

Hi, Andreamaz

Thanks for your quick feedback at last time.

Now I want to adjust the animateWithDuration(default is 0.15) setting for slide animation in my instance class.
But it is difficult.

How about to make the default setting more extendent in SlideOutNavigation?

It would be nice to have the all badge totals read out on the iconSlide button. Nice work on the rest!

Works perfectly on iPhone, but on iPad the views are stretched past the viewable bounds. See attached screen shot.

This is true for all of the views added to the slideoutnavigation controller. They are also all table view controllers if that makes any difference.

Hi,
this is not really an Issue, more a question :)

Is it possible to manipulate the navigation "on the fly"?
For example, adding menu items after a login procedure?

Thanks :)

Hi @andreamazz
SlideOutNavigation has serious performance issue.

I've modified your StroryboardExample project:

• added FirstViewController for the first view
• put UITableView
• implemented required delegates, datasource

You can download it from my dropbox folder here.

Steps to reproduce:

1. Download project and run it.
2. Scroll through table with slow speed that should still scroll ~2-3 row after you release finger/mouse pointer.

Actual: It works very slow on iPhone 4 and iPhone 4s with ugly lags. You can't see them on iPhone 5 but seems like because it has better hardware.
You can see them also in simulator on video I've prepared here.
Expected: No lags, no performance issue.

Is there a way to programmatically navigate to a view controller? I've tried:

[slideoutController setCurrentViewController:myViewController];

and also:

[[slideoutController navigationController] popToViewController:myViewController animated:YES];

Neither seem to work.

@andreamazz I'm looking at your amazing changes 👍 but I see that SlideoutStoryboardSample has compilation errors from the box.