Android Actionbar Search widget implementation In ListFragment

后端 未结 1 718
梦毁少年i
梦毁少年i 2021-01-29 22:23

I currently have my application set up with a ListFragment on the left and a DetailsFragment on the right (similar to the layout on the tablet below).<

相关标签:
1条回答
  • 2021-01-29 23:08

    Yes, as a matter of fact, that is the "normal" use case. What you have to remember is that the fragment that uses the search action bar widget, should be the part that registers it in general, since the widget will get destroyed along with that fragment.

    Here's how to properly tie it up:

    in your ListFragment let it be known that you have option menu items...

    @Override
    public void onActivityCreated(Bundle savedInstanceState) {
        ..
        setHasOptionsMenu(true);
        ..
    }
    

    then inside the same ListFragment create your options menu by overriding the callback, once you have the SearchView widget reference, register a QueryTextListener callback:

    @Override 
    public void onCreateOptionsMenu(Menu menu, MenuInflater inflater) {
        inflater.inflate(R.menu.grid_default, menu); 
        SearchView searchView = (SearchView)menu.findItem(R.id.grid_default_search).getActionView();
        searchView.setOnQueryTextListener(queryListener);
    }
    

    create your search widget via either programmatically (Java) or declaratively (XML) here is XML (named grid_default.xml, from above):

    <?xml version="1.0" encoding="utf-8"?>
    <menu xmlns:android="http://schemas.android.com/apk/res/android">
    
        <item     
            android:id="@+id/grid_default_search"
            android:icon="@android:drawable/ic_menu_search"
            android:title="search"
            android:showAsAction="always"
            android:actionViewClass="android.widget.SearchView" 
        />
    
        <!-- other items or whatever  -->
    
    </menu>
    

    now back in your ListFragment you need to create the queryListener we registered above:

    private String grid_currentQuery = null; // holds the current query...
    
    final private OnQueryTextListener queryListener = new OnQueryTextListener() {       
    
        @Override
        public boolean onQueryTextChange(String newText) {
            if (TextUtils.isEmpty(newText)) {
                getActivity().getActionBar().setSubtitle("List");               
                grid_currentQuery = null;
            } else {
                getActivity().getActionBar().setSubtitle("List - Searching for: " + newText);
                grid_currentQuery = newText;
    
            }   
            getLoaderManager().restartLoader(0, null, MyListFragment.this); 
            return false;
        }
    
        @Override
        public boolean onQueryTextSubmit(String query) {            
            Toast.makeText(getActivity(), "Searching for: " + query + "...", Toast.LENGTH_SHORT).show();
            return false;
        }
    };
    

    now you know when a query is changed or submitted, in my example, I re-query anytime a key is pressed because my database was small and fast with results, you might need to change this.. but you'll notice how I am just using the widget to set a private class field inside the ListFragment to the current text of the search widget (grid_currentQuery) and then I am just calling getLoaderManager().restartLoader(0, null, MyListFragment.this); where inside my onCreateLoader I am just updating the query I used like this:

    @Override
    public Loader<Cursor> onCreateLoader(int id, Bundle bargs) {
    
        String sort = "SortColumn ASC";
        String[] grid_columns = new String[] { "ColumnA", "ColumnB", "Etc..." };
        String grid_whereClause = "ColumnToSearchBy LIKE ?"
    
        if (!TextUtils.isEmpty(grid_currentQuery)) {            
            return new CursorLoader(getActivity(), DataProvider.CONTENT_URI, grid_columns, grid_whereClause, new String[] { grid_currentQuery + "%" }, sort);
        }       
    
        return new CursorLoader(getActivity(), DataProvider.CONTENT_URI, grid_columns, null, null, sort);
    }
    

    and that's all you really need to do, I realize this is kind of chopped up but it's like this because there is more stuff that needs to happen, setting the adapter, starting the loader in the first place using getLoaderManager().initLoader(0, null, this); and all the rest of the loader callbacks that need to be handled... but if you are following the best practices set forward by the android folks, (using LoaderManagers in your ListActivitys and ListFragmentss it should be pretty easy for you...

    I hope this helps feel free to ask for clarification in the comments if you need to -ck

    0 讨论(0)
提交回复
热议问题