google-code-export / tatami

Automatically exported from code.google.com/p/tatami
1 stars 1 forks source link

Chart2D Not Rendering in IE8 #40

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I have a Chart2D within a cell in a VerticalPanel, which, in turn, is the 
primary child of a PopupPanel. It happens to be a line chart. This chart 
renders just fine in Safari 5.0.5, Chrome 12.0.742.100 and FireFox 4.0.1. It 
does not render in IE8. I am also using a Slider widget (not on the 
PopupPanel), which renders just fine in all browsers.

I am using GWT 2.3.0 and Tatami 1.4.

I have tested Safari, Chrome and FireFox on Mac OS X 10.6.7.
I have tested IE8 and FireFox on Windows XP and Windows 7.

Joel Rives
jmrives@gmail.com

Original issue reported on code.google.com by jmri...@gmail.com on 16 Jun 2011 at 7:20

GoogleCodeExporter commented 9 years ago
I have additional information regarding this issue.

I am seeing the following error: 'this.rawNode.path' is null or not and object.

This is occurring at eval code, line 8 character 8698.

At this location, I see the following assignment: 
this.rawNode.path.v=_4d.join(" ");

Original comment by jmri...@gmail.com on 16 Jun 2011 at 7:40

GoogleCodeExporter commented 9 years ago
Hi, I'm having this same problem, have you discovered any further information 
or some kind of workaround? I haven't seen an error myself though.

Original comment by kyle.saw...@gmail.com on 2 Sep 2011 at 5:45

GoogleCodeExporter commented 9 years ago
No, I have not found a solution for this problem. I opted to make use of GWT 
Graphics, which is a vector graphics library for GWT. You can find it here: 

    http://code.google.com/p/gwt-graphics/

Joel

Original comment by jmri...@gmail.com on 2 Sep 2011 at 7:47

GoogleCodeExporter commented 9 years ago
If anyone else ever happens to read this. I fixed it by modifying the choice of 
renderer that tatami makes in the charting_module js file. If you make IE9 use 
SVG, IE8 use canvas, and IE7 use VML it should work in all of them.

Original comment by kyle.saw...@gmail.com on 15 Sep 2011 at 4:53

GoogleCodeExporter commented 9 years ago
Kely, how did you do that (specifying renderer per browser)?   I'm stumped with 
an in house app that I've written.  FFX/Chrome/Safari are all great. IE 8 blows.

Original comment by chris.fa...@gmail.com on 1 Feb 2013 at 9:01

GoogleCodeExporter commented 9 years ago
Kyle, too.   Ugh. sorry.. dead brain today

Original comment by chris.fa...@gmail.com on 1 Feb 2013 at 9:46

GoogleCodeExporter commented 9 years ago
Hmm, I'm not entirely sure at this point, I wish I had written more detail back 
then. My guess is I was talking about a file which may not actually be used any 
more. It does look like you can fiddle around with gfx.js though, which is 
located in trunk/tatamiJS/src/com/objetdirect/tatami/public/dojox/gfx.js

Alternatively, there is a file called tatami_charting_module.js which has some 
references to dojox.gfx.renderer but it looks like it's in a sample folder so 
I'm not sure how useful that's going to be.

Original comment by kyle.saw...@gmail.com on 1 Feb 2013 at 11:44

GoogleCodeExporter commented 9 years ago
We solved this problem by moving the render() call from postCreate() into 
startup(). I guess there are certain widgets that are not available until 
startup().

Original comment by AnthonyD...@gmail.com on 15 Jan 2015 at 9:09