Open GoogleCodeExporter opened 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
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
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
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
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
Kyle, too. Ugh. sorry.. dead brain today
Original comment by chris.fa...@gmail.com
on 1 Feb 2013 at 9:46
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
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
Original issue reported on code.google.com by
jmri...@gmail.com
on 16 Jun 2011 at 7:20