Quantcast
Channel: Tools
Viewing all articles
Browse latest Browse all 91752

Forum Post: RE: ccs memory inspection windows is hard to handle

$
0
0

Hello Alexander, 

I wanted to thank you for your effort in sending us feedback on how to improve CCS. I have couple of suggestions for you that might make some issues that you raised easier to live with. CCS is based on eclipse, which we keep unmodified. This allows for quicker update cycles. The main downside is that some features have options that we probably would remove if we had full control. Memory view is a feature that is somewhat flexible and we have been able to add some functionality to it, but it has some other quirks that we "inherit". Now as far as suggestions:

I would suggest that you use New View functionality rather than a New Tab. The button to open new instance of memory view is just above "Go" button. This will open a new view rather than a new tab. It has couple of advantages. 1) address box will stay in synch with what is shown as there will be only one tab. 2) You can re-arrange these views like any other view. If you use a multi-cpu device, then you can have one memory view pinned to CPU A and another that follows selected CPU in Debug View. It also makes it easier to compare memory as you can arrange views side by side. 

Two other issues 

a) renaming of views/tabs

b) re-using last entered data format

are still outstanding. I'll file enhancement requests for these. 

Martin


Viewing all articles
Browse latest Browse all 91752

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>