Closed anderserla closed 10 years ago
Have you managed to reproduce this error @sweco-sebhar ?
No never seen it :(
We dont act on it any more right now. Wait and see if it will appear again.
I think we'll have to look into this problem a little bit more.
There are more users reporting problems with search. It often happens when the user makes a new search before the answer of the previous has returned.
Would it be possible to put a longer delay between stop writing and start searching?
Ok I'll try to reproduce. How would it help increasing the delay?
Ok I think I understand what is going on now. If a new search is triggered and is responding faster than a previously issued but unfinished search the results presented will be overwritten by the first search.
If the above is correct I think there is two possible ways to fix it:
I'll try to implement alternative 1.
Alternative 1 cannot be done without changes in Ext JS 4 (afaik), so I implemented alternative 2.
OK The delay is so short that it often happens that a search starts before the user stops writing, resulting in multiple searches. It happens because it is hard to type an estate expression without pause, cus there are often letters, digits and colons included in the expression.
Works for me. I will let some other users verify this too.
What is the time to make alt 1? And is it possible to put it back into ExtJS source? and time for that?
I think it would be better to use the previous solution, rather than this fix. It is too confusing for the end user. Back code to be as it was before the fix.
Add some time for the delay. Maybe 0.8 secs?
After that put some time to analyse alt 1.
Changes reverted and delay changed to 800 ms.
Implemented workaround (alternative 1) described here: http://stackoverflow.com/questions/15237011/extjs-4-remote-combobox-abort-previous-request
Works perfect for Fastighet. Not implemented for Adress and Ortnamn?
Då ska de vara fixat!
Great!
The users have had problems searching parcels in Sundsvall at some occations. Se attached image.