|
Query |
Response |
|
I have discovered a difference: this is because I'm using connectors creation instead of using DataSourceSettings.Parent. After this all works as expected. Another issue is I wonder how to set labels to nodes? As I use nodes without labels in some cases I can't use it's names as Id. I tried several solutions, but unsuccessfully. In attachment you could found my asp sample.
I'm using 15.4.0.17 version. If it is crijtial to update, then tell me know. |
You can set labels for node in nodeTemplate function which triggers for each and every node. We have modified your code example.
Code example:
EliminationChart.js
function nodeTemplate(diagram, node) {
node.labels[0].text = node.Labels[0].Text;
}
Here is the sample for your reference
Help documentation:
|
|
I also discover another feature is not more working. I need to use callbacks with your chart and also using it with DevExpress xaf. Early we have already found solution for this: set nodes to chart, convert to JSON and store in hidden field. On loading we have just restore this json (https://www.syncfusion.com/forums/133298/diagram-and-callbacks). All works well, but on change it to store, I get "Uncaught SyntaxError: Unexpected token e in JSON at position 381 at JSON.parse (<anonymous>)" exception. Could you tell me how could I resolve this? |
Could you please confirm us whether you are facing an issue while loading the diagram? If so, please provide us more details such as how you are serializing the JSON object and share your JSON which you have parsing it using JSON.parse or else please modify the sample provided in the first row. |
|
Query |
Response |
|
I have applyed your changes to my application and need to fix json parsing to 'eval' method using, because your json is contains "ej.isJSON" string ("...'dataSourceSettings':{"dataSource":ej.isJSON([{"Shape":0,..."), but I can't just send this object to function, because I'm using hidden field with string objects. Is it possible to use JSON.parse method here somehow? This json string is not looks as appropriate for flexible using. Eval is not safe... (https://stackoverflow.com/questions/45015/safely-turning-a-json-string-into-an-object). It is apporpriate solution for now, but would be cool to solve this issue. |
|
|
I also wonder is it ok to use old version dlls (15) with new scripts (16)? |
No, please use dll and script files of same version. We have missed to change it in our previous sample. |