Currently Activities are being leaked for as long they are kept in the queue, this PR aims to fix this issues by:

• Auto releasing it onDestroy for ICS+, older versions must call cancelAll(Activity) (preferred) or cancelAll() at earliest convenience.
• Using one MsgManager per Activity, this way Activity A won't have to wait for AppMsgs belonging to Activity B to be removed in order to show A's AppMsgs
• Also updates gradle files/vars

It's a Fatal Exception: Main.

And the cause is:

java.lang.NoClassDefFoundError: com.devspark.appmsg.R$color
    at com.devspark.appmsg.AppMsg.<clinit>(AppMsg.java:52)

Any ideas?

I added the possibility to use custom layout for the message, since it has an TextView with the android.R.id.message. I also added the feature of using an in-layout View, instead of a floating View for the message. If this new feature is used, the custom view will be hidden, instead of removed from the layout. So, it can be reused as many times as the user wants to. I also fixed the behavior of the clear() method, since it wasn't removing the message when it was being shown.

This proposed patch will allow the out animation to actually be visible on screen. Originally, the out animation was attached to the view using view.startAnimation(). Immediately following that, the message is removed from the queue and the view is removed from the parent. In most cases, the view is removed from the parent before the animation is visible on screen, thus the resulting effect is the view suddenly disappearing from the screen instead of playing the animation.

Hello! The following pull request is to add support for using user defined animations instead of always using the default fade in/fade out animations. If no user defined animation is set, it will default back to the fade in/fade out animations that were originally there.

This is some code to enable the caller to have a bit of control over the placement of the AppMsg by specifying LayoutParameters. There is also a helper method provided in the case where all you want to change is the layout gravity, for example to show the AppMsg at the bottom of the Actitivy.

I was reading Appolo-CM, which imported AppMsg from here. But in Appolo-CM the class Crouton is needed. And I looked for Crouton in AppMsg here and there but found nothing about it. So, where is it or does Crouton exist in another projects?

I'm trying to display the crouton on child fragment it's not displaying anything

//=================================

//activity-->viewpager fragment--->childfragment /calling crouton here/

MeetingFragment f = new MeetingFragment();

AppMsg.makeText(f.getActivity(), "Hello AppMsg",AppMsg.STYLE_ALERT,(ViewGroup) f.getView()).show(); //failed in nested fragment

Crouton.makeText(getActivity(), "Hello Crouton", Style.INFO,(ViewGroup) getView()).show(); //failed in nested fragment

//=================================

http://stackoverflow.com/questions/14760042/appmsg-crouton-library-support-for-fragments-urgent

any solutions to make it available for fragment or child (nested) fragment ?!! or this will still display the crouton for the activity, not for an individual fragment?

This is some preliminary support for building AppMsg with gradle, for use in the new Android build system.

In particular, if gradle is on your PATH and the Android SDK is set up properly, you can now do gradle :library:assemble to build the AppMsg library, and then you can include it in your projects.

Not supported yet:

• building the sample project (because it relies on ActionBarSherlock, which is not yet easily available as an AAR, though support for this is pending, see JakeWharton/ActionBarSherlock#891)
• publishing an AAR of AppMsg itself to Maven Central or something like that

I can work on these two issues (especially the latter) later, but the patch included here is sufficient to let me build my app with AppMsg, so hopefully it will be useful to someone else even in this limited state.

In my application i have a fragment dialog with some controls. Controls make possibility to chose some data and has button. This button validates entered data and make message if data is not valid. But there is a bug (maybe it's feature) - message is appeared under dimmed background of this dialog. Is it possible to show message over the dimmed background.

Merge this to receive a badge indicating the number of issues in the ready column on your waffle.io board at http://waffle.io/johnkil/Android-AppMsg

This was requested by a real person on waffle.io, we're not trying to spam you.

When I move from one activity to another very fast, the app msg showing there keeps there FOREVER, even I use cancelAll() or cancelMsg(). What is the solution. Please help me.

As I have not seen any example of positioning the messages in a custom view, I want to share how I solved the problem to get inputs from other users. I am not sure if this is the proper way but it works for me.... more or less:

I added this code to the layout embedded in a RelativeLayout:

                      <!-- required by AppMsg to position in another place -->
                      <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
                          android:id="@+id/messagescontainer"
                          android:layout_width="match_parent"
                          android:layout_height="wrap_content"
                          android:layout_centerInParent="true">

                          <include layout="@layout/app_msg"/>

                      </LinearLayout>

and this code into the Java

            LinearLayout messagesContainer = (LinearLayout) findViewById(R.id.messagesContainer);

            AppMsg.makeText(OfferActivity.this, "Error Performing this Operation", AppMsg.STYLE_ALERT, carouselContainer).show();

However, there seems to be a bug because the message is shown as soon is instantiated in makeText(), without the need to call show() method. However, you need to call show() in order to make cancel() method work. Otherwise, cancel() does not remove the message.

Are these bugs or I am not using it in the proper way?

Hi, I have created two AppMsg object like below,

public MyActivity extends Activity {
     AppMsg noConnectionMsg, connectedMsg; 

    @Override
    public void onCreate(Bundle bundle) {
      noConnectionMsg = AppMsg.makeText(this,
                getResources().getString(R.string.msgNoConnection),
                AppMsg.STYLE_ALERT);

        noConnectionMsg.setDuration(AppMsg.LENGTH_STICKY);


        connectedMsg = AppMsg.makeText(this,
                getResources().getString(R.string.msgConnected),
                AppMsg.STYLE_INFO);
    }

   ...
   ...

}

But when I run the application, notifications are successfully shown. After cancelling the AppMsgs, App is getting crashed with this Error:

Attempt to invoke virtual method 'boolean com.devspark.appmsg.AppMsg.isShowing()' on a null object reference.

I am using the makeText method with OnClickListener, but I recently switched to gradle and it appears that these methods are not present in Maven Central repository, I can only use the methods without OnClickListener.

Is it possible to make a new release with these changes?