I think we have identified the problem. I've tested with a simple scene that has just a string node exposed as an external. I tried looping through the XML file and setting the external to a substring of the entire file - I had a hunch it might be to do with the maximum buffer size of the GDI DrawString() function
http://msdn.microsoft.com/en-us/library ... s.85).aspx
So, I started working around the 32k limit (32768 bytes), and that was too long. With some trial and error, and lots of Ventuz restarts, it seems that there is an absolute limit of 32000 characters.
My next test was to work out why. So, I did the same tests with a formatted text file - and all was fine. I could send my entire 70k test file! Bear in mind I've now eliminated the XMLText node, as I'm testing with String node. So, it's definitely a issue with the property window, nothing to do with the XMLText node or the XML Parser.
My last test was to format the offending XML using an XMLTextWriter before setting the external. It worked! Still the same data, but with a line break after each element.
The conclusion then, I think, is that there is a hard *line length* limit of 32000 characters on the string parameter of the DrawString method.
Your thoughts on this greatly appreciated!
Cheers,
Craig.
