It was moved into gwt-incubator here: http://code.google.com/p/google-web-toolkit-incubator/source/browse/trunk/src/com/google/gwt/widgetideas/client/RPCSuggestOracle.java
It is using the SuggestBoxOverride as its base, which is basically SuggestBox but copied to incubator to allow us to add some extra features we needed. On Thu, Sep 4, 2008 at 12:30 PM, Isaac Truett <[EMAIL PROTECTED]> wrote: > @Oscar > You might be interested in Emily's patch a few months ago on the > contributor's list: > > > http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/83db777f0e0602d0 > > > @Emily > I never saw this patch committed. Did something happen off-list to put > the kibosh on it? I've looked for a related issue and couldn't find > one in the tracker. I think this is the second time in as many weeks > that I've referred someone to the patch as a possible aid to their > suggestion-related problems and I've been using it for months without > ill effect. Is this still on anyone's radar? > > > > > > On Thu, Sep 4, 2008 at 1:52 AM, Oscar <[EMAIL PROTECTED]> wrote: > > > > Solved it! My bad... > > > > For anyone else who gets stuck on this problem, the answer is that you > > need to provide some sort of sequencing in your SuggestOracle/ > > Callback. What I ended up doing was maintaining a sequence number in > > the SuggestOracle and passing the current sequence number into the > > callback. Then before the RPC Callback writes its results to the > > Suggest Callback, ensure that its sequence number is >= the current > > sequence number in the Suggest Oracle. This way, if newer results > > come in before older results, only the newer results will ever be > > displayed. > > > > This is obviously due to the fact that the RPC is async, so you have > > no guarantees on when you will end up receiving your suggestions. All > > in all, an easy solution to the problem and it seems to make the > > widget flow a little nicer in the application since the suggestions > > dont end up fluttering so much. > > > > > > On Sep 3, 9:58 am, Oscar <[EMAIL PROTECTED]> wrote: > >> Sorry if this post appears twice... I posted yesterday, and now I > >> can't find it! :) > >> > >> I am having a problem using GWT's SuggestBox on FF3 when the custom > >> SuggestOracle calls an RPC on a webserver that is geographically far > >> away. What seems to be happening is that an earlier query completed > >> AFTER the final query, which ultimately results in the wrong > >> suggestions being displayed. > >> > >> For example, assume "X" displays 20 results, and "XYZ" displays 1 > >> result. If the user types "XYZ" really quickly, multiple RPC requests > >> will be sent to the webserver, which is fine. I can see these > >> requests being processed, and I can see each one of them sending the > >> correct results back to the client. However, the suggestions that end > >> up being displayed are the results for the "X" or "XY" query, not > >> "XYZ". Has anyone else encountered this? Any idea how to resolve > >> it? So far I have only been able to reproduce this issue with FF3, > >> but if it is an ordering issue, it should be reproducible with any > >> browser. I will try to test this later today to make sure, but I was > >> hoping someone else has seen this problen and resolved it already. > > > > > > > -- "There are only 10 types of people in the world: Those who understand binary, and those who don't" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
