The data table's setValue function, which get a string as the third argument, is implemented by directly calling the javascript implementation as you can see here: http://www.google.com/codesearch#ow6Lmd7dcZY/trunk/visualization/visualization/src/com/google/gwt/visualization/client/DataTable.java&l=198
This means that there should be no difference in the actual code between debug and regular modes. Maybe store the strings as a temporary string variable before passing it to the setValue function. Is it possible that the returned value is not string and therefore a different method is being called? (and the difference between debug and regular executions are automatic castings) Viz Kid On Fri, Jul 29, 2011 at 5:15 AM, xiaochen wang <[email protected]>wrote: > Hello Viz Kid > > i use smartgwt and google visualization. i write the code in eclipse. i run > the project in debug mode in eclipse. it works fine. then i compile the > project and run it. it stuck at the line dataTable.setValue(i, 0, > arrName[i].toString()); > > from the sample code, you could see that i add log before the line. the log > message is printed out. after that the log stop. i have some log after the > for loop. > > many thanks > > xiaochen > > On Thu, Jul 28, 2011 at 10:17 PM, Viz Kid <[email protected]> wrote: > >> >> 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. >> > > -- > 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.
