Subject: Simplified Protection | Term-Life Policy: 250K Available

From: Jayla <[email-masked]>
Date: Wed, 21 May 2014 08:41:15 -0700

Greetings Ipp-archive,

You have reached a life milestone which now qualifies you for a low Term-Life Rate.

View Rate Here: http://www.yupole.com/policy/update/500k.html

Rate Generated on: May 20, 2014

- Please note that this rate is set to expire.
-- The available $500,000+ is immediately available.
--- To view all details of policy click here: http://www.yupole.com/policy/update/500k.html

-to modify your message settings - w/ Alert System Notifications
(write) one one zero seven  V a l e r  i a  Drive Marion, TX 78124
(or) http://www.yupole.com/jf3.gnek

Is the actual problem that you just don't want it to have focus at all? Or you don't want it to show the virtual keyboard as a result of focusing the EditText? I don't really see an issue with the EditText having focus on start, but it's definitely a problem to have the softInput window open when the user did not explicitly request to focus on the EditText (and open the keyboard as a result)

If it's the problem of the virtual keyboard, see the AndroidManifest.xml <activity> element documentation.

android:windowSoftInputMode="stateHidden" - always hide it when entering the activity

or android:windowSoftInputMode="stateUnchanged" - don't change it (e.g., don't show it if it isn't already shown, but if it was open when entering the activity, leave it open)Bravo! I noticed that Eclipses' WYSIWYG editor adds this line automatically. Removing it worked like a charm, thanks!   DzinX Jun 15 '12 at 10:32
2	  	
This appears to be the best solution in most cases. Would be nice if it was more visible. Thanks @DzinX for the comment pointing this out.   Aaron Dufour Jun 19 '12 at 15:46
  	  	
Of course, the way to just not have this issue is to just use XML instead of the graphical editor. The graphical editor isn't worth crap and certainly can't be considered in the same league as Apple's interface builder for iOS / OS X. Upvoting Joe for pointing out a real solution for whether you're using graphical or XML.   ArtOfWarfare Sep 18 '12 at 19:37 But this will never gain focus in future, how to just stop focus only for initial(activity start) ??   Jayesh Mar 8 '13 at 7:46
1	  	
The onTouchListener is called before other touch actions. So by enabling focusable on touch the standard focus happens on the first touch. The keyboard will come up and everything.   MinceMan Mar 9 '13 at 16:36
1	  	
I think this is the best way to do it. Also, the mumbo-jumbo xml magic dummy code above did NOT work for a complex set of edit texts...If this works, I will definetely vote up.   Radu Jul 29 '13 at 9:02
 final ViewGroup content = (ViewGroup)activity.findViewById(android.R.id.content);
     final View root = content.getChildAt(0);
     if (root == null) return null;
     final View focusDummy = new View(activity);
     final View.OnFocusChangeListener onFocusChangeListener = new View.OnFocusChangeListener()
     {
         @Override
         public void onFocusChange(View view, boolean b)
         {
             view.setOnFocusChangeListener(null);
             content.removeView(focusDummy);
         }
     };
     focusDummy.setFocusable(true);
     focusDummy.setFocusableInTouchMode(true);
     content.addView(focusDummy, 0, new LinearLayout.LayoutParams(0, 0));
     if (root instanceof ViewGroup)
     {
         final ViewGroup _root = (ViewGroup)root;
         for (int i = 1, children = _root.getChildCount(); i < children; i++)
         {
             final View child = _root.getChildAt(i);
             if (child.isFocusable() || child.isFocusableInTouchMode())
             {
                 child.setOnFocusChangeListener(onFocusChangeListener);
                 break; 	  	
not working in ics simulator   Yogesh Maheshwari Nov 26 '12 at 7:32
  	  	
This works for me. I had already set the keyboard to not appear, but I had an edittext at the bottom of a scrollview and the page would always scroll down to the edittext. This fixed it. Thanks for pointing this out.   Reynard Dec 10 '13 at 18:36 In Android applications such as Twitter (official app), when you encounter a ListView, you can pull it down (and it will bounce back when released) to refresh the content.I wonder what is the best way, in your opinion, to implement that?Some possibilities I could think of:An item on top of the ListView - however I don't think scrolling back to item position 1 (0-based) with animation on the ListView is an easy task.
Another view outside the ListView - but I need to take care of moving the ListView position down when it is pulled, and I'm not sure if we can detect if the drag-touches to the ListView still really scroll the items on the ListView.Hi johan, I have downloaded your sample code. It is worked in android 2.2 device but not worked in 2.1 device. I think because it used smoothScrollBy method which only available in 2.2 or later, is correct? And do you have any idea to implement this effect into 2.1 or earlier version? Thanks   user577394 Jan 16 '11 at 15:18Yes that's correct as I stated in the answer smoothScrollBy was introduces in API Level 8 (2.2). I haven't figured out a proper way to implement it for other versions yet, but it guess it should be possible to port the implementation of smoothScrollBy but I guess that discussion should be kept at the project site and not on stack overflow?   Johan Nilsson Jan 16 '11 at 18:0Is it on purpose that the id is @+id/android:list and not @androi
 d:id/list, it looks weird? The project throws an inflation error here on my side, I'm currently checking on that...   Mathias Lin May 17 '11 at 9:28
9	  	This is the best library for pull to refresh  works with ListViews, GridViews and Webviews. Also has Pull up to refresh pattern implemented.   gaurav Apr 1 '12 at 23:07 
 	How do I add the project into library folder while working on Intellij Idea? Can anybody help me?  
Any recommendationsP.S. I wonder when the official Twitter app source code is released. It has been mentioned that it will be released, but 6 months has passed and we haven't heard about it since then.