This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ccs memory inspection windows is hard to handle

when doing a certain job i am often setting up a memory window to keep certain data in a permanent watch.

when setting up the first sub-tab for the memory tab then i am selecting some base address and a data format. Enter or go-button will make it apear...

but when setting up a second item the data format is not cloned from the first one (which would be rather rational and handy) but some default format is choosen. - this could see improvement as its likely that a certain format selection will be re-used in the next window as well.

when having several such sub-tabs open i am not able to re-arrange their order at all. no dragging possible. - this could be quite helpful feature as all other tabs already do support it.

when clicking along serveral sub-tabs the headline of those tabs might be very is often abbreviated and no hint for what the full line would be. neither is there any way for editing the headline into some easy to remember name nor is the current formula that leads to the display editable. the properties tab i have open simply apears to be empty. - this could be improved. image analyzer is a good example on how it can be done. (the input box for the address formula often displays data from some other operation, but it does help only with some luck to get the prior inputs by its drop down button. in fact the input box is often misleading about whats displayed as it is not at all in sync with the current window. compare to common web browsers - the visible & editable address window is bound to the tab and changes to the new context when clicking other tabs.)

  • 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