Ann BZ

Thanks - I downloaded the latest version since it has been updated. However, I still see the same issue outlined in #1 above. The label seems bound to the image size, rather than the node size. Is this a bug - or am I doing some thing wrong? I am attaching the xml I am using to render the chart, and a screen capture of what I see rendered. Thanks, Ann Data.xml

Thanks much for the information. Right now I am using the trial of PowerCharts ... I am trying to evaluate it for a project I am working on . Would it be possible to evaluate the latest drag node chart code for my evaluation?

Hi - I have the following observations when using labels for nodes in a drag node chart ... can someone please comment on if this is working behavior - or a bug? or if there are suggested workarounds? 1)When using an image for the node, it appears as though the area dedicated to the label is constrained by the image height & width (imageWidth, imageHeight) rather than the node height/width (width, height). The problem I have observed with this is that if you are using static images ... to represent some common item - such as a server, but there are varying names for each server, the names will not render appropriately unless the size of the image is somehow adjusted (which does not look visually appealing) - or a very tiny font is used (which is unreadable on the glass). I understand that the name/label can be obtained by hovering over the node (or one can adjust font size) ... but this certainly decreases the value of printing out something like a network topology... 2) when using a node without an image specified ... the labelAlign property appears to have no affect ... the label is always placed vertically in the middle 3) The documentation refers to a "label" property on the "set" element ... but this appears to be ignored and rather "name" property is used... Thoughts? A

I was wondering what type of scalability testing has been done with the Drag Node Charts. For example, how many nodes and connectors can be viewed at one time - what type of client side CPU is consumed for large charts? What type of features in the chart would slow performance? Also wonder if there is a mechanism to expand the context menu on a node - ie, add new menu options that would link to javascript functions? Thanks, Ann