Skip to main content

(Vibrating TextView) Configure attributes for custom views


I just created class VibratingTextView . I intend to create a whole library of widgets so I want to do it the right way.



The xml for this View:




<sherif.android.textview.VibratingTextView
android:id="@+id/textView2"
android:layout_width="wrap_content"
android:textAppearance="?android:attr/textAppearanceLarge"
android:layout_height="wrap_content"
android:orientation="horizontal"
android:text="outToRight" >
</sherif.android.textview.VibratingTextView>



Notice it has android:orientation and android:text . It accepts the attributes of a TextView and of a LinearLayout . The class itself extends LinearLayout .



My problem is in the xml editor of eclipse. When the user types android: , eclipse's intellisense gives the user the options available in this namespace.



In my case, it is giving the attributes of LinearLayout so, for example, Text and TextSize do not appear.



Is there a way to make them appear (using the android namespace)?



If not, should I create my own namespace with attributes that I define? or is there a way to import the android's attributes and make them in sherif's attributes?



Keep in mind that I am creating a TextView in the constructor of my class using the attributes passed. It is working fine and all the attributes for the TextView are being set correctly.



Since I will create many other widgets, I might need my own namespace but what is the best practice? For example, I want to create alwaysVibrate attribute. It will be something like sherif:alwaysVibrate="true" . I want my library to be includable and eclipse to show the attributes of my namespace: I use the usual way using attr.xml ?


Source: Tips4allCCNA FINAL EXAM

Comments

  1. I recently faced the exact same problem. Here are my custom attribute declarations in attrs.xml

    <?xml version="1.0" encoding="utf-8"?>
    <resources>
    <declare-styleable name="NumberPicker">
    <attr name="rangeStart" format="integer|reference" />
    <attr name="rangeEnd" format="integer|reference" />
    <attr name="speed" format="integer|reference" />
    <attr name="current" format="integer|reference" />
    <attr name="android:orientation" />
    </declare-styleable>
    </resources>


    You can reuse the android attributes but you can't teach them to suggest different values. In fact you can't even teach eclipse to suggest your custom attribute definitions (at least at this date of post, I would love to see that feature in future).

    Everything else you would want to know about defining custom attributes is in the question:
    Declaring a custom android UI element using XML.

    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