I have react-infinite-scroll-component with my table result and I have also a filter to do a search. My issue is once I scroll a little and hit the search button, search call is triggered by both search button and infinite scroll next
I'm using version 6.1.0 react-infinite-scroll-component
Related
In this video I first click on a field within the first tab, then click the soft keyboard's "check" button. This hides the soft keyboard and takes the focus away from that field. I then navigate across tabs and back to the first. No field has the focus at this point. This is the expected behavior.
In the second iteration, I click in the notes field. Without closing the soft keyboard, I then click the submit button. That button calls FocusScope.of(context).unfocus(); which hides the soft keyboard and takes the focus away from the notes field (the teal border disappears). However, at this point I click on the next tab and the soft keyboard reappears. And when I click back the first tab the notes field once again has the focus.
Why does this happen?
What underlying code does the "check button" on the keyboard call and can I wire this up to the button rater than calling the .unfocus() method to get the expected result?
Edit: Still no explanation. The undesirable persistent keyboard does not occur on iOS.
I have a Text Field with _searchController and a separate IconButton that clears the _searchController:
_placesList are the search results.
I also have a method _onSearchChanged that is a listener for the _searchController:
The _onSearchChanged method calls another method that makes an API call if the search controller is not empty:
When the cancel icon button is pressed, I found (through debugging) that the search controller listener is triggered before the search controller text is cleared and therefore an API call is made and THEN the search controller text is actually cleared.
This leaves a list of unwanted search results on the screen.
Hitting the cancel icon button a 2nd time results in the desired outcome of clearing the search results. But obviously I don't want the user to have to press the cancel icon button twice.
I want the cancel icon button to clear the search text and the search results.
I believe you are missing setState here.
Simply wrap the _searchController.clear(); in it like tihs:
setState( () {_searchController.clear();} );
Otherwise flutter won't rebuild with the new data.
This is a common mistake that people forget about.
I have an update panel with some text entry boxes, a clear button and a save button. Under the boxes I have a repeater that holds database entries. When a user enters data in the textboxes and clicks the Save, a database row is created and the repeater rebinds and shows the new dataset. There are buttons on each repeater row for "Delete" and "Edit". When the Edit button is clicked on a row, the data from that row is populated back into the text boxes. When I do that, the autocomplete extenders stop working. I have a button that simply clears the textboxes. If I click that button and clear the textboxes, the autocomplete starts working again. Even if I remove all code from that "Edit" button in the repeater command and don't have it populate the text boxes from the row clicked, the autocomplete stops working. Something is happening on the item command for the repeater row that is turning off the autocomplete. Any suggestions?
I had some javascript functions running from the code behind on page load. Moving that from the server side page load to the javascript pageLoad() function fixed the issue
(Duplicate of this question, but I figured I could try again, since that one wasn't answered...)
The UISearchBar on the iPhone has an option showsSearchResultsButton. When you turn it on, it shows a button with horizontal lines inside the search bar, and you can implement a callback that will be called when the user presses it.
The thing is, I can't find a single place on the Internet where it says what the intended purpose of this button is. I know I could make it do anything, but I'd like to know what it's actually for. Should it show a history of searches, or all items without filtering, or what?
It's simply to show search results when tapped.
Where Apple uses this is in their iPad App Store application. If you go to the Categories tab you'll see various app categories. Search for an item, you'll get a list of results, and when you press "Done" you are shown the categories screen again. Your previous search term is still listed in the search field, but now the Search Results Button appears in the field. After tapping this, a UIPopOver is displayed, showing a text list of the results from your last search.
I have a UISearchBar that searches and displays results successfully. If I press the cancel button mid-search, the original table is restored and all is well. If I press the search button that is on the keyboard, the search results are shown, which is great. But THEN if I press the cancel button that is on the search bar (I am using the 'search bar and display controller'), the screen goes back to normal, leaving behind only the search results and not showing the original table.
Any ideas?
Thank you!
I got it - I did not know where I could interact with the cancel button that was built into the search bar but I put code that cleaned out the search table in the -searchButtonPressed and threw that in under the search did its work!