Thanks Chris

On 12/20/2010 2:46 PM, Chris Conroy wrote:
Chrome checks the profile directory to figure out if it needs to start a new session or attach to an existing one. You should be fine having an instance of Chrome open with an instance of Chromium since they use different profiles. If you want to have multiple instances of Chrome or Chromium, then simply launch your alternate with --user-data-dir=/path/to/alternate/profile/directory

OK - that makes sense. I made the comment below because I spent about an hour this morning experimenting with older nightly builds to try and find one that still worked (and didn't have any other problems.) I found that unless I was careful to make sure that I'd closed the previous nightly build I was getting conflicting results because double-clicking on XXX when I had YYY already open of course meant that I was still using YYY. In other words, I wasn't trying to have *multiple* entries open, I was just needed to make sure that the entry I had open was *different* from the previous try. As I said below 66202 seems to work. I tried 66482 for a while, but the debug console didn't seem to work properly on that. 66202 is 9.0.584.0 (66202). As a matter of interest, I couldn't find *any* version with "10." in it which didn't show http://code.google.com/p/google-web-toolkit/issues/detail?id=5778 - but then, you probably already know that!


Regards

Alan



On Mon, Dec 20, 2010 at 5:19 PM, [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]>> wrote:

    Go to http://build.chromium.org/f/chromium/snapshots/chromium-rel-xp/ and 
find a snapshot that
    works for you.

    I'm currently using  66202, dated Nov 15 2010

    Open the folder labeled 66202, download the zip file, extract it and then 
navigate to
    Chrome.exe and use it.
    Experience indicates that its best:

    1. To *NOT* have any other copies of Chrome/Chromium open before you open 
this one.
    2. Stop any dev mode projects you have (that is, stop them running), close 
any current
    versions of Chrome/Chromium, open the nightly as above and then start dev 
mode again. I don't
    believe that you need to restart eclipse.

    I'm using 66202, but you may find a later one works for you - remember that 
these are nightly
    builds and may not work at all!

    Hopefully the issue will be resolve shortly....

    HTH

    Alan



    On 12/20/2010 9:33 AM, funkforce wrote:

        Same problem here. Is there a way to go back to old Chrome? Doesnt get
        it to work in FF 4 beta also.

        On Dec 20, 5:44 pm, "[email protected]
        <mailto:[email protected]>"<[email protected] 
<mailto:[email protected]>>
        wrote:

            Sadly, that doesn't work for me because I am developing a WebGL 
based app and that
            only works with
            Chrome or FF 4.

            I've  reverted to an earlier nightly build until the issue is fixed.

            And, of course, I'm wondering when FF4 will be supported in GWT - 
but that's another
            story (and
            thread) entirely. In August I heard it was "real soon now"...

            Alan

            On 12/20/2010 8:26 AM, Thomas Broyer wrote:

                Or temporarily switch to Firefox 3.x ;-) --
                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]
                <mailto:[email protected]>.
                To unsubscribe from this group, send email to
                [email protected]
                <mailto:google-web-toolkit%[email protected]>.
                For more options, visit this group
                athttp://groups.google.com/group/google-web-toolkit?hl=en
                <http://groups.google.com/group/google-web-toolkit?hl=en>.



-- 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]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to 
[email protected]
    <mailto:google-web-toolkit%[email protected]>.
    For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


--
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.


--
Alan Chaney
CTO and Founder, Mechnicality, Inc.
www.mechnicality.com

--
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.

Reply via email to