I finally got rid of MPLAB and am now using Microsoft's Visual Studio IDE=
=2E =20
Just because I do most of my development in that and am used to it.  CCS =
C=20
will integrate into it with minimal effort.  Just add an 'External Tool'.=
 =20
You can then take advantage of VS's auto-complete, auto-tab and=20
variable/keyword highlighting.  I use Warp-13 to program the PIC, so it's=
=20
just a matter of having VS and Warp-13 open.  When CCS C compiles, switch=
 to=20
Warp-13 and it updates the new HEX file for programming.

Barry

On Thursday 06 February 2003 01:42 pm, you wrote:
> As a side note, none of them work well with MPLAB. I personally think M=
PLAB
> is one of the worst IDE's that I have used. I develop for about a dozen
> different microcontroller families and MPLAB has the worst features, mo=
st
> bugs and worst integration for source level debugging of all of them.
> Microchip has been "fixing" MPLAB since I became a Microchip consultant
> almost 10 years ago. I'm disappointed that a company the size of Microc=
hip
> can't develop a better tool than MPLAB has evolved into. As a compariso=
n,
> take a look at the tools available for the AVR or TI's MSP430 family.
> There's just no comparison.
>=20
> Matt Pobursky
> Maximum Performance Systems

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads