What do you mean by compiled vs. debug modes? The visualization API should always be in the same mode, and therefore if you have such a change in behavior, it might be related to what your code returns in these two cases.
Viz Kid On Thu, Jul 28, 2011 at 9:59 AM, xiaochen wang <[email protected]>wrote: > sample code > > for(int i=0; i<arrName.length; i++){ > //Log.debug(arrName[i].toString()); > //Log.debug(dataMap.get(arrName[i])+""); > > dataTable.setValue(i, 0, arrName[i].toString()); > dataTable.setValue(i, 1, dataMap.get(arrName[i])); > > } > > the program will suspend at the first setValue function. > but if change to > dataTable.setValue(i, 0,"ABC"); > the program can run properly. > > the phenomenon only occurs when run the compiled files. it is ok in > debug mode. > > -- > 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.
