🚀 go-pugleaf

In article <mwron-0510001318260001@c243286-a.bcreek1.mi.home.com>,
  mwron@metrowerks.com (MWRon) wrote:
> In article <nick-0510001342400001@nessus.peramon.com>,
nick@lexicos.com
> (Nick Emery) wrote:
>

> >I'm developing a Java application. In CW5.3 I used the deprecated
> >MetroNub debugger primarily because the speed of the default
> >debugger (using the Sun Java Debugger API) was abysmal.
>
> It is poor but not abysmal I've not getting the results you are on a
> slower machine with 5.3.
>
> >When I upgraded to CW6, I assumed that the same performance problems
> >would exists for the default debugger, and so I also installed the
> >deprecated MetroNub debugger again.
>
> By this do you mean you use the one in the Thrill Seekers folder or
you
> installed the one from 5.3.  If you did the one from 5.3 that is
probably
> the reason.  If you did the one from the Thrill seekers, be sure you
> installed it correctly you just add the plugins you don't need to use
a
> different MetroNub.
>

The same thing is happening with me.  I installed the deprecated
debugger following the directions in the Thrill Seeker folder.

And the default debugger is also painfully slow for me.


.
.
.


Sent via Deja.com http://www.deja.com/
Before you buy.