Skip to main content

findViewByID returns null


first of all: yes, I read all the other threads on this topic. And not only those from this site... (you see, i'm a little frustrated)



Most of them come with the advice to use "android:id" instead of just "id" in the xml file. I did.



From others, i learned, that View.findViewById works different than Activity.findViewById . I handled that, too.



in my location_layout.xml i use




<FrameLayout .... >
<some.package.MyCustomView ... />

<LinearLayout ... >
<TextView ...
android:id="@+id/txtLat" />
...
</LinearLayout>
</FrameLayout>



in my Activity i do




...
setContentView( R.layout.location_layout );



and in my custom view class:




...
TextView tv = (TextView) findViewById( R.id.txtLat );



which returns null. Doing this is my Activity works fine . So maybe it's because of the Activity.findViewById and View.findViewById differences. So i stored the context passed to the customs view constructor locally and tried




...
TextView tv = (TextView) ((Activity) context).findViewById( R.id.txtLat );



which also returned null.



then i changed my custom view to extend ViewGroup instead View and changed the location_layout.xml to let the TextView be a direct child of my custom view, so that the View.findViewById should work as supposed. Suprise: didn't solved anything.



So what the heck am i doing wrong ?



I'll appreciate any comments.



regards, Thomas ;)


Source: Tips4allCCNA FINAL EXAM

Comments

  1. which returns null


    Possibly because you are calling it too early. Wait until onFinishInflate(). Here is a sample project demonstrating a custom View accessing its contents.

    ReplyDelete
  2. Make sure you don't have multiple versions of your layout for different screen densities. I ran into this problem once when adding a new id to an existing layout but forgot to update the hdpi version. If you forget to update all versions of the layout file it will work for some screen densities but not others.

    ReplyDelete
  3. Possibly, you are calling findViewById before calling setContentView?
    If that's the case, try calling findViewById AFTER calling setContentView

    ReplyDelete
  4. A answer for those using ExpandableListView and run into this question based on it's title.

    I had this error attempting to work with TextViews in my child and group views as part of an ExpandableListView implementation.

    You can use something like the following in your implementations of the getChildView() and getGroupView() methods.

    if (convertView == null) {
    LayoutInflater inflater = (LayoutInflater) myContext.getSystemService(Context.LAYOUT_INFLATER_SERVICE);
    convertView = inflater.inflate(R.layout.child_layout, null);
    }


    I found this here.

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?

CCNA 1 Final Exam 2011 latest (hot hot hot)

  Hi! I have been posted content of ccna1 final exam (latest and only question.) I will post the answer and insert image on sunday. If you care, please subscribe your email an become a first person have full test content. Subcribe now  Some question  have not content because this question have images content. So that can you wait for me? SUNDAY 1. A user sees the command prompt: Router(config-if)# . What task can be performed at this mode? Reload the device. Perform basic tests. Configure individual interfaces. Configure individual terminal lines. 2. Refer to the exhibit. Host A attempts to establish a TCP/IP session with host C. During this attempt, a frame was captured with the source MAC address 0050.7320.D632 and the destination MAC address 0030.8517.44C4. The packet inside the captured frame has an IP source address 192.168.7.5, and the destination IP address is 192.168.219.24. At which point in the network was this packet captured? leaving host A leaving ATL leaving...