It's super slow for me also - sometimes the content assist window will
hang for up to ~30s (in Eclipse 3.5, it takes just a few hundred ms max)
meaning that 3.6 is not usable for Android development at the moment (if
there are no workarounds..).
I've found the following bug for Eclipse regarding this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=317979 but I have no idea
if it's an Eclipse bug or an ADT bug that just happens to be triggered
by Eclipse 3.6 for some reason. Maybe Xavier wants to enlighten us ? :)
On 7.08.2010 2:16, Zsolt Vasvari wrote:
This happens with me also, only sometimes. I don't know if this is
Helios or the Android stuff, but developing with Helios has more
nagging issues than Galileo has.
On Aug 6, 10:00 pm, Evan Ruff<evan.r...@gmail.com> wrote:
After upgrading to Helios, my code assist is dog slow as well.
I am currently experimenting with the location of Eclipse (was on D,
moving to C) as well as the memory args...
E
On Jul 8, 7:27 am, gDev<sab...@gmail.com> wrote:
CodeAssistveryslow
any soluation for that?- Hide quoted text -
- Show quoted text -
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
