Positioning of the nested concepts

Have new ideas for the next release of IHMC CmapTools and IHMC CmapServer?
We welcome your suggestions and we will carefully consider whether to incorporate them into the software.
Post Reply
Posts: 4
Joined: Sun Mar 06, 2011 2:07 pm

Positioning of the nested concepts

Post by JeffN » Sun Mar 06, 2011 2:33 pm

At the moment when you create a concept with nested concepts, then expand it and move it to a new location on the map, the collapsed concept remains at its old location. I think it would be much more intuitive if both were moving together.

Posts: 4
Joined: Sun Nov 10, 2013 10:33 am

Re: Positioning of the nested concepts

Post by ubiquity » Mon Jun 30, 2014 2:58 am

There are pro's and con's here.
Sometimes the collapsed nest needs to remain behind the centre of the original bounding box for the nest, which is where it is created by default.
Like you I often need to move both items but I suspect if I was using CMapTools strictly for its designated purpose this may not be an issue.
It also depends on whether one is nesting existing concepts or adding some after the nest has been created.
In my case I am using it to link concepts created on the OpenIDEO crowd sourcing platform.
They are created ad hoc in response to an initial provocation so this means many reconfigurations of grouped or nested concepts.

Posts: 1
Joined: Mon Oct 20, 2014 12:09 am

Re: Positioning of the nested concepts

Post by dany500 » Mon Oct 20, 2014 12:13 am

Off and on again the given way home needs to stay behind the inside of the first jumping box for the home, which is the place it is made naturally.

Like you I regularly need to move both things however I think on the off chance that I was utilizing Cmaptools strictly for its assigned reason this may not be an issue.


Post Reply