Giter Club home page Giter Club logo

ffglobalalertcontroller's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

ffglobalalertcontroller's Issues

carthage version

could you please let me know if its carthage version is available?

unrecognizerSelectorSentToInstance

Hey agilityvision, thanks for the pod. Here's the error I'm getting:

-[UIAlertController show]: unrecognized selector sent to instance 0x1614660e0

2016-02-15 15:21:29.155 AppName[17087:3765939] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIAlertController show]: unrecognized selector sent to instance 0x1614660e0'

I'm calling alert.show() on a UIWindow. Not sure why I'd be getting this. Any advice?

Key Window not resigning

This solution worked for me until I started compiling my code with Xcode 7 for iOS 9. Now it seems that the key window for the new alert never resigns. In my app this makes it so that I am unable to tap through to underlying views after I show an alert.

I was able to learn more by observing the following notifications:
[[NSNotificationCenter defaultCenter] addObserverForName:@"UIWindowDidBecomeVisibleNotification" object:nil queue:[NSOperationQueue mainQueue] usingBlock:^(NSNotification *notification) {
NSLog(@"UIWindowDidBecomeVisibleNotification");
}];
[[NSNotificationCenter defaultCenter] addObserverForName:@"UIWindowDidBecomeHiddenNotification" object:nil queue:[NSOperationQueue mainQueue] usingBlock:^(NSNotification *notification) {
NSLog(@"UIWindowDidBecomeHiddenNotification");
}];
[[NSNotificationCenter defaultCenter] addObserverForName:@"UIWindowDidBecomeKeyNotification" object:nil queue:[NSOperationQueue mainQueue] usingBlock:^(NSNotification *notification) {
NSLog(@"UIWindowDidBecomeKeyNotification");
}];
[[NSNotificationCenter defaultCenter] addObserverForName:@"UIWindowDidResignKeyNotification" object:nil queue:[NSOperationQueue mainQueue] usingBlock:^(NSNotification *notification) {
NSLog(@"UIWindowDidResignKeyNotification");
}];

Multiple targets match implicit dependency

@agilityvision
I am using 'pod FFGlobalAlertController' in the Podfile for a B2B iPad app. It is working wonderful, but in Xcode 11 beta 3 (which has just been released for developers) I am getting the warning:

Target Integrity Group
Multiple targets match implicit dependency for 'FFGlobalAlertController'. Consider adding an explicit dependency on the intended target to resolve this ambiguity.

  • Target 'FFGlobalAlertController-FFGlobalAlertController' (in project 'Pods')
  • Target 'FFGlobalAlertController' (in project 'Pods')

xcode-target

This did not happen in Xcode 11 beta 2. Does anyone have a clue how to solve it?

-show and -show:animated not called

Hi

I was using your UIAlertController presentation approach when ran int problem:
When accessibility's Darken Colour's option is OFF I need to inherit window's tintColor, otherwise - use UIAlertController's default. So I added this code to show:animated method:

if ( !UIAccessibilityDarkerSystemColorsEnabled() )
{
    self.alertWindow.tintColor = delegate.window.tintColor;
}

The problem is - show and show:animated methods are not executed despite the alert is shown. Can it be somehow associated with ObjC runtime which is used to make associated property?

autolayout issue?

Just got this on the 9.2 simulator:

This application is modifying the autolayout engine from a background thread, which can lead to engine corruption and weird crashes. This will cause an exception in a future release.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.