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

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex