Closed GoogleCodeExporter closed 9 years ago
Original comment by galgwt.reviews@gmail.com
on 2 Jun 2009 at 12:45
have plans to solve this?
this problems appears using gwt and java script
Original comment by fot...@gmail.com
on 2 Jun 2009 at 1:02
It would be a big help if you could provide some source code that reproduces
the
issue.
Original comment by galgwt.reviews@gmail.com
on 2 Jun 2009 at 1:04
http://fother.googlepages.com/gauge.html
click in the button, you can see that the formattedValue disappears, view the
source
code..
you did it reproduce?
Original comment by fot...@gmail.com
on 2 Jun 2009 at 1:08
its one issue?
Original comment by fot...@gmail.com
on 2 Jun 2009 at 1:35
I see, this sample page isn't using GWT, its using straight JavaScript calls,
so the
problem is probably not with the GWT bindings. I tried several things but
couldn't
make it work. I've assigned it to a member of the Visualization team for
further
study:
var data;
var gauge;
function drawVisualization() {
// Create and populate the data table.
data = new google.visualization.DataTable();
data.addColumn('string', 'Label');
data.addColumn('number', 'Value');
data.addRows(1);
data.setValue(0, 0, 'Example');
data.setValue(0, 1, 40);
data.setFormattedValue(0,1,'$ 40.00');
// Create and draw the visualization.
gauge = new
google.visualization.Gauge(document.getElementById('visualization'));
gauge.draw(data, null);
}
function test() {
data.setValue(0, 1, 80);
data.setFormattedValue(0,1,'$ 80.00');
gauge.draw(data, null);
}
google.setOnLoadCallback(drawVisualization);
Original comment by galgwt.reviews@gmail.com
on 2 Jun 2009 at 1:44
ok.. I will create a GWT example.. but the behavior its the same..
you click in the button and see that don't appears $80.00 in the gauge? only
set the
value equals 80?
Original comment by fot...@gmail.com
on 2 Jun 2009 at 1:50
Yes, thanks, I did see the problem using Chrome 1.0.154 on Windows XP. There's
no
need to make a GWT example right now. If the JavaScript API doesn't work, the
GWT
API won't either.
Original comment by galgwt.reviews@gmail.com
on 2 Jun 2009 at 1:56
good! I believe that this problems appears in all browser I test in firefox
3.0.10,
ie 8 and the behavior its the same.. have plans to correct this? have other
locale to
post this issue?
thanks, regards
Original comment by fot...@gmail.com
on 2 Jun 2009 at 2:01
followups to the visualization team...
Original comment by zundel@google.com
on 7 May 2010 at 3:39
Original issue reported on code.google.com by
fot...@gmail.com
on 2 Jun 2009 at 12:18