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.

CCSTUDIO: ICONS are rearranged, and will not change

Part Number: CCSTUDIO
Other Parts Discussed in Thread: ENERGYTRACE

Ki,

For years, I've been using a couple of specific workspaces. Lets call it A and B

Then I created a new one.  Lets call it C.  Nothing special...  just open a new folder and it makes a workspace out of it...

And I have this difference between A and C  (or between B and C).

Notice the icons are rearranged??   Workspace 'A' is on top, and it's the one I'm used to.

No matter how many times I drag them to where I want them, they don't stay.  I exit and restart, and it's back to the old way.

This is EXTREMELY annoying that controls are rearranged.

It guarantees that you will hit the wrong button.

And to make things WORSE, I can rearrange the buttons on workspace A and they WILL stay after I exit and restart.

So in other words... I can change Workspace 'A' to button configuration that I DON'T want... but I can't change workspace 'C' to button configuration that I do want...

What's it take to get some consistency?

  • This looks like a bug. I can reproduce it. I would expect the icons to remain where you moved it to.

    For workspace "A", I assume this is a workspace that was first created from an older CCS version while "C" was created with the current version.

    There is a hack you can do to an xml file in your workspace metadata to move stuff around. It's an ugly hack but if you are interested, let me know.

    I will file a bug for this issue.

    Thanks

    ki

  • Tracking link for the bug:

    https://sir.ext.ti.com/jira/browse/EXT_EP-10494

    Thanks

    ki

  • Okay then...

    Is there a workaround?  A hack I can use?

    One workspace has it the way I want it.  I'd like to be able to make the others that way as well.  I assume those settings are buried in those workspace files somewhere.  So I should be able to edit them manually.

  • Christopher,

    Ki is out today but will be back tomorrow and can let you know which file he was editing for his workspace metadata.

    Regards,

    John

  • Is there a workaround?  A hack I can use?

    I played around with the hack a bit more today. It is a really crappy hack and not very reliable or consistent. I'd rather not recommend it anymore.

    But if you still want to experiment with it a bit...

    With CCS closed, open the below xml file:

    <WORKSPACE DIR>\.metadata\.plugins\org.eclipse.e4.workbench\workbench.xmi

    In the above file, search for "TrimBars". Beneath that are a bunch of "children" tags. Each of these represent toolbars or items that appear in the toolbar area. You can try rearranging the ordering of the tags, which will control the ordering of the toolbar icons.

    <trimBars xmi:id="__bqZo_nfEeuP579H1cPQ9g" elementId="org.eclipse.ui.main.toolbar" contributorURI="platform:/plugin/org.eclipse.ui.workbench">
    <children xsi:type="menu:ToolBar" xmi:id="_AZX_EPngEeuP579H1cPQ9g" elementId="group.file" toBeRendered="false">
    <tags>toolbarSeparator</tags>
    <children xsi:type="menu:ToolBarSeparator" xmi:id="_AZX_EfngEeuP579H1cPQ9g" elementId="group.file" toBeRendered="false"/>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_AZYmIPngEeuP579H1cPQ9g" elementId="org.eclipse.ui.workbench.file">
    <tags>Draggable</tags>
    <children xsi:type="menu:HandledToolItem" xmi:id="_AZcQgPngEeuP579H1cPQ9g" elementId="print" visible="false" iconURI="platform:/plugin/org.eclipse.ui/icons/full/etool16/print_edit.png" tooltip="Print" command="__cLXNPnfEeuP579H1cPQ9g"/>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_AZYmIfngEeuP579H1cPQ9g" elementId="group.edit" toBeRendered="false">
    <tags>toolbarSeparator</tags>
    <children xsi:type="menu:ToolBarSeparator" xmi:id="_AZYmIvngEeuP579H1cPQ9g" elementId="group.edit" toBeRendered="false"/>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_AZYmI_ngEeuP579H1cPQ9g" elementId="org.eclipse.ui.workbench.edit" visible="false">
    <tags>Draggable</tags>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_AZYmJPngEeuP579H1cPQ9g" elementId="additions" toBeRendered="false">
    <tags>toolbarSeparator</tags>
    <children xsi:type="menu:ToolBarSeparator" xmi:id="_AZYmJfngEeuP579H1cPQ9g" elementId="additions" toBeRendered="false"/>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_AkbYgPngEeuP579H1cPQ9g" elementId="com.ti.ccstudio.project.ui.projectBuildActionSet">
    <tags>Draggable</tags>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_AkuTcPngEeuP579H1cPQ9g" elementId="com.ti.dvt.energytrace.actionSet">
    <tags>Draggable</tags>
    </children>
    <children xsi:type="menu:ToolBar" xmi:id="_Ak6gsPngEeuP579H1cPQ9g" elementId="org.eclipse.search.searchActionSet">
    <tags>Draggable</tags>
    </children>
    ....

     

    For example, the section in bold represents the EnergyTrace button. If I move it higher up, it will move the button more to the left in the GUI. However, It is not clear to me what represents some of the other toolbars. Some of them I can't find the section that represents them. It was difficult for me to precisely put the button exactly where I wanted it. 

    As mentioned, it's a pretty unreliable hack to me. CCS is always overwriting the file when the workspace is saved. 

    Sorry for the pain. It is indeed quite annoying.

  • Ki,

    Now you know why I despise XML...  And the people who cryptically put stuff in it.

    What's the point of have data/metadata/content/etc...  in a readable text file, if it's unreadable to a user???  DUH!!  This is the kind of software engineers the education system is cranking out...

    Anyway, enough of that rant...  :-) 

    CCS is always overwriting the file when the workspace is saved.

    So, even if I changed it, it wouldn't stay.

    So I suspect that the ones in the order I prefer were the ones created by CCS7.  And the new ones created by CCS 10 are the ones that are wrong.  So I tested it.

    Yes.

    I opened the brand new workspace with the old CCS7, got that warning, said "sure go ahead and change it..." and moved the icons.  Then closed it.

    Then I opened it again with CCS10, got that warning, said "sure go ahead..."   and the workspace now has the icons in my preferred order.

    So I have a more viable workaround at this point.  At least for those of us who have a leftover CCS 7 sitting on the drive.

    Thanks.

  • So, even if I changed it, it wouldn't stay.

    Not quite. The changes made manually would have gotten read and applied to the workspace. The when the workspace is saved, it would save the existing state of the workspace to the xml file. But it doesn't get preserved the way I was expecting.

    In any case, yes - cryptic indeed.

    I opened the brand new workspace with the old CCS7, got that warning, said "sure go ahead and change it..." and moved the icons.  Then closed it.

    Then I opened it again with CCS10, got that warning, said "sure go ahead..."   and the workspace now has the icons in my preferred order.

    So I have a more viable workaround at this point.  At least for those of us who have a leftover CCS 7 sitting on the drive.

    Glad that works for you. It is not something we'd recommend because reusing a workspace from a much older version of CCS can cause all sorts of issues. But your use case may be fine since all that is happening is creating a new workspace in v7, moving some icons around and the opening it again in v10. No project imported or any other changes. this would minimize risk of some workspace migration issues.

    Thanks

    ki