Consider the case of specifying a parent. If multiple parent nodes have the same name, how do you decide what the parent is?
On Wed, Jun 22, 2011 at 1:19 PM, NA <[email protected]> wrote: > Yes, but this seems like a problem with Treemap. The Treemap should > realize that each row represents a different node (that's how the data > is specified). It should "unique-ify" the data on its own, perhaps by > internally combining the row number with the value. > > However Treemap does this, it's part of implementing a Treemap and > shouldn't be something that each user of the Treemap would have to > reinvent on his/her own > > FormattedValue is just a workaround for this problem. Not a pretty > one, either, as it involves first junking up your Treemap datasource, > and then trying to clean it up with formatters... > > > > > > > > On Jun 20, 5:24 pm, Tayeb Karim <[email protected]> wrote: >> GoogleVisualization's DataTable allows a distinction between a value >> and a formatted value. >> You can use the FormattedValue to be the display name, whereas the >> Value can be used to unique-ify the element. >> >> >> >> >> >> >> >> >> >> On Fri, Jun 17, 2011 at 9:07 AM, Csaba Balogh <[email protected]> wrote: >> > Well that's exactly the way i solved the problem... thank you! >> >> > 2011/6/17 MarkC <[email protected]> >> >> >> I've stumbled across the same problem - and has gone down the 'making >> >> the values non-unique' route.... essentially concatenating with the >> >> parent node value. >> >> Not ideal... but gets round the problem >> >> >> On May 26, 10:45 pm, NA <[email protected]> wrote: >> >> > Suppose that your DataTable has repeated values for some leaf nodes. >> >> > Thetreemapcombines those leaves together under each parent node for >> >> > which any of them appear. This means that the leaf nodes appear under >> >> > parent nodes that they do not belong to. >> >> >> > It appears that there is an assumption being made internally by >> >> > thetreemapcode that the values for the leaf node are unique. This may >> >> > not be the case - instead, uniqueness can be guaranteed by combining >> >> > the value along with the row number. >> >> >> > Are there any workarounds to this? I can prob post an example if this >> >> > is really needed, but I suppose that by now this may be a known >> >> > issue. >> >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> >> "Google Visualization API" group. >> >> To post to this group, send email to >> >> [email protected]. >> >> To unsubscribe from this group, send email to >> >> [email protected]. >> >> For more options, visit this group at >> >>http://groups.google.com/group/google-visualization-api?hl=en. >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Google Visualization API" group. >> > To post to this group, send email to >> > [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> >http://groups.google.com/group/google-visualization-api?hl=en. >> >> -- >> - >> --- >> Tayeb Al Karim >> [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-visualization-api?hl=en. > > -- - --- Tayeb Al Karim [email protected] -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
