>>joe,
from your post it's my guess that you are using a CCS version 2.x (x4). everything you've mentioned in your post was addressed in CCS 3.0 which was released to market quite some time ago.
of most interest to you would be the editor update to Codewright and connect/disconnect. most causes of crashes with earlier versions of CCS were due to drivers not being very elegant with flaky devices. connect/disconnect gives one a way to cleanly disconnect from a device, power cycle it to get to a good state and then reconnect without affecting the IDE.
however there are some inacurracies that i'd like to point out - debugging both cores never required separate versions of CCS running at the same time.
i definitely saw a lot of stability improvements.
i'm curious, how many qa personell do you think would be required to test a complex product, especially if there are combinations of supported devices and OSs?
Slashdot Mirror
>>joe, from your post it's my guess that you are using a CCS version 2.x (x4). everything you've mentioned in your post was addressed in CCS 3.0 which was released to market quite some time ago. of most interest to you would be the editor update to Codewright and connect/disconnect. most causes of crashes with earlier versions of CCS were due to drivers not being very elegant with flaky devices. connect/disconnect gives one a way to cleanly disconnect from a device, power cycle it to get to a good state and then reconnect without affecting the IDE. however there are some inacurracies that i'd like to point out - debugging both cores never required separate versions of CCS running at the same time. i definitely saw a lot of stability improvements.
i'm curious, how many qa personell do you think would be required to test a complex product, especially if there are combinations of supported devices and OSs?