With the exception of:

(with ICS2 and 18F parts)

If a breakpoint can't be set when you click run, ASK the user if the run
should in fact happen.  Rather than just going w/o breakpoints!  aargh!
  Stupid stupid!  (this happens when there isn't a 1 to 1 for C source
and a place in program memory, CCS PCH does this often, not sure if
other compilers are better).

And a way to jump to where in source a breakpoint shown in the
breakpoint list is set at, i.e. select (disabled) breakpoint and click
"go here".  Omg what a timesaver that would be.

The only other problem - over the course of hours of run, stop, reset,
cycle it takes longer and longer to start running (several seconds) and
then MPLAB will crash.

J


Walter Banks wrote:
> Mplab 6.xxx is starting to come together.
>
> w..
>
> Jan-Erik Soderholm wrote:
>
>
>>Hi.
>>Anyone having anything good/bad to say about MPLAB 6.50 ?
>>
>>Regards,
>>Jan-Erik.
>>
>>PS.
>>Have you noticed that the "development tools" page at MC,
>>*always* says "New MPLAB. IDE available now!"...
>>And you *always* have to enter the page to see if there
>>realy *is* a new MPLAB, which in 99 times out of 100 there
>>is not... :-) :-)
>>
>>--
>>http://www.piclist.com hint: PICList Posts must start with ONE topic:
>>[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>
>

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics