As it is now, all unconnected nodes end up at the root level which is really annoying when you are working with larger trees.
5 Answers, 1 is accepted
Probably the only hack right now is to make the shape you don't want to lay out invisible before calling Layout() and turn them back on thereafter. The layout does not take the hidden shape into account.
Thanks for this feedback, Fr.
We haven't included such changes within the layout mechanism so far. However, we logged your suggestion in our PITS where you can vote for it in order to increase its priority and you can also track its progress.
I also updated your Telerik account for sharing your feedback.
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.
I'm thinking of something like this:
I'm not sure how I would set up the container, but adding all connected nodes would be a first step. Ideas?
Thank you for your suggestion. We would definitely take it into consideration. There are several possible approaches here.
One would be to use some kind of connected graphs (like you are suggesting with the container graph) and pass those graphs to the layout. Personally I think this would be the most convenient way to customize the layout. Of course a default or empty container/graph could be used to layout all shapes.
Another approach would be to provide some kind of descriptor. The descriptor could be accountable to define how different types of shapes should be handled.
Also a protected method on the layout also could be exposed in order to customize the items collections before layout happens.
However, we would have to evaluate each one of them before implementing the most appropriate one. Currently I am not able to state which approach is going to be implemented.
Please let us know if you have more feedback or ideas on the topic.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>