Skip to main content

Using resources referenced in the current theme



I find myself again trying to use resources set in the current theme inside my Android application and running into difficulties.





Following the rough guidelines found here for theme attribute value reuse





I was originally trying to create a selector like so







<?xml version="1.0" encoding="utf-8"?>

<selector xmlns:android="http://schemas.android.com/apk/res/android">

<item android:state_pressed="true" android:drawable="?android:attr/selectableItemBackground" />

<item android:drawable="@color/transparent" />

</selector>







where the pressed state drawable is declared like so







<item name="selectableItemBackground">@android:drawable/item_background</item>







in the current ICS themes xml doc themes xml doc . This compiles fine in eclispse (whereas if i spell the attr wrong it will give an error or reffng @android:drawable/item_background directly will inform me the drawable itself is private).





When i run the app i get a







FATAL EXCEPTION: main

E / AndroidRuntime (18815): android.view.InflateException: Binary XML file line #14: Error inflating class <unknown>







without any other useful information apart from the xml file that is using this selector for an ImageViews android:background attribute value. I know that there is a bug where colorStateLists cant be used as backgrounds as mentioned here and maybe this also applys to drawableState lists referencing drawables from the theme. I know however it does work as the post mentioned describes.





Am i missing something here?? I always run into something i dont understand when trying to do stuff like this so would be glad of any pointers.





Thanks for any help





EDIT





as another experiement I tried setting an alias to the referenced drawable in the theme like







<?xml version="1.0" encoding="utf-8"?>

<bitmap xmlns:android="http://schemas.android.com/apk/res/android"

android:src="?android:attr/selectableItemBackground" ></bitmap>







and using this as the background directly but this does not work either. Looking at aliases they are onlyment to ref actual images so this makes sense





EDIT 2





another test an I have found using it directly







android:background="?android:attr/selectableItemBackground"







does actually work. So it seems that using it inside a alias or selector is where it gets unhappy. Strange as i would assume that both background and the same arg





EDIT 3





It seems the theme attr i was pointing at was actually a selector instelf, which im sure didnt help the issue! Thought i wouldve guessed looking at the name of it


Comments

  1. I guess i answered the question myself in my edits - main issue i imagine was that i was trying to ref a selector inside a selector.

    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