Spinner for Dropdown

Spinner helps you to display the set of data (collection). It allows teh data to be displayed in drop down fashion.
Example:
1. Lets define a static String array in Android XML file.




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

     <resources>
       <string-array name="countries">
        <item>India</item>
        <item>U.A.E.</item>
        <item>Nepal</item>
        <item>China</item>
        <item>Australia</item>
        <item>United States</item>
        <item>Europe</item>
        <item>United Kingdom</item>
        <item>Australia</item>
        <item>Canada</item>
        <item>Japan</item>
        <item>Singapore</item>
      </string-array>
    </resources>



2. Configure Spinner in your activity XML file.     




<Spinner    
android:id="@+id/location_spinner"    
android:layout_width="wrap_content"    
android:layout_height="wrap_content"
android:background="@android:drawable/btn_dropdown"
android:spinnerMode="dropdown"    />













background attribute is used to define background for the Spinner. If not specified, the spinner will not be a defined background else if specified, will appear as below-                          










With background








without Background



















spinnerMode attribute is used to control the fashion in which the dataset should be displayed. That is, dropdown or dialog. In case of 'dropdown', the values will be shown in dropdown fashion and in case of 'dialog', the values will be shown in a dialog box [values are not shown as attached items to the field holder (spinner)],












attribute = 'dialog'








attribute='dropdown'











3. Configuring the Spinner in Java








private void initialiseLocationSpinner() {
    Spinner dropdownSpinner = (Spinner)findViewById(R.id.location_spinner);

    // Spinner element
    String[] items = getResources().getStringArray(R.array.countries);

    // Creating adapter for spinner
    ArrayAdapter<String> dataAdapter = new ArrayAdapter<String>(this, android.R.layout.simple_spinner_item, items);

    // Drop down layout style
    dataAdapter.setDropDownViewResource(android.R.layout.simple_spinner_dropdown_item);

    // attaching data adapter to spinner    
    dropdownSpinner.setAdapter(dataAdapter);

   // Spinner click listener
    dropdownSpinner.setOnItemSelectedListener(new AdapterView.OnItemSelectedListener() {
        @Override
        public void onItemSelected(AdapterView<?> parent, View view, int position, long id) {
                // On selecting a spinner item
                String item = parent.getItemAtPosition(position).toString();

                // Showing selected spinner item
                Toast.makeText(parent.getContext(), "Selected: " + item, Toast.LENGTH_LONG).show();
        }










































Comments











Post a Comment



















Popular posts from this blog









@Overrride annotation introduced in Java1.5 





















 Whenever we have a subclass that implements parent method it is marked with annotation as @Override. This is to make compiler know that the child overrides the method defined or declared in parent.   If @Overrride annotation is commented, the subclass will work as it was.  But if in future, the signature of parent class changes, the compiler wont ask to implement the method instead it will think subclass has overloaded the method present in base class.   If you uncomment @Override annotation, the compiler will throw compile time error as method signature in parent class has changed.   Annotation should be used as standard as-    It ensures that for any change in method signature of parent class, compiler will ask to change it for the subclasses.     Also it is better to resolve issue in compile time rather than runtime    








Read more










Open-Closed Principle





















  'A class should be open for extension closed for modification.'    The above principle explains that a class once defined should not be changed(closed for modification). This is because it may impact other parts of application.  Hence, if modification is needed, that class behaviour should be extended and modification should be done. (open for extension)   Consider a scenario where area of a shape(like rectangle, square, circle) is calculated within Main class. Now addition of any new shape will lead to change in Main class. This concludes that the Shape is tightly coupled with Main class.   In order to avoid this Shape should be inherited by diff Shape classes like Rect, Triangle, Circle implementing the behaviour of calculating area() and Main class should be loosely coupled by using Shape.area() (as Triangle, Rectangle are Shape).  Hence, Shape interface is contract between its concrete classes and Main class. This allows us to add new shape class without any impact on exi...








Read more










S.O.L.I.D. Class Design Principles 





















      Abbreviation    Full Form    Definition    Reason      S   Single Responsibility Principle  A class should have only one reason to change i.e. should have only one purpose to serve.   - loosely coupled  - less change lead to less break down of application  - helps to change identity of object without affecting other modules        O   Open-Closed Principle  A class should be open for extension closed for modification.  - Anyone need to make change in your class has to inherit the class and change. This allows the existing functionality to stay intact.     L   Liskov Substitution Principle  Derived types should always be substitutable by its parent class (base type).  Derived types should be compatible with its base type.  For e.g.: Square is a Rectangle i.e. Square represents a Rectangle.  In case, if we try to set dimension of a Rectangle reference pointing to Square instance, the flow will be weird as it will always override the dimension of rectangle.     I   Interface Seg...








Read more