__data__.getData debugging

Hi,

I have the following problem with __data__.getData():

When I have a bug in the PHP code which supplies the data to
__data__.getData(), the HTML code displaying the PHP Error of course
evaluates to null and is returned as null to the callback function. Is there
a way to preserve the unparseable code, so that I could log it or display it
in a debug window? I tried tgtNode.firstChild.innerHTML which I found in the
__data__.getData() code, but it is always empty when the callback function
is called. It would be good to have a global variable containing the HTML
content retrieved.

Thanks,

Christian 



> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Christian Boulanger
> Sent: Monday, September 29, 2003 10:05 AM
> To: 'netWindows development discussion list'
> Subject: RE: [NW-Devel] split pane widget
> 
> 
> Hi all,
> 
> I solved my persistent split pane widget problem. As it turns 
> out, I did not call the fixHeight() method after attaching 
> the NW_WIDGET_FACTORY_split_pane to the parent window. After 
> doing this, I got rid of (almost) all display bugs (except 
> douple scroll bars which appear sometimes). IE works w/o 
> problem now. So it was my mistake after all. Alex, make sure 
> to highlight this in the manual for programmatic construction...
> 
> Best,
> 
> Christian 
> 
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Alex Russell
> > Sent: Wednesday, August 20, 2003 9:47 AM
> > To: [email protected]
> > Subject: [NW-Devel] split pane widget
> > 
> > 
> > So after a bit of hacking and mucking, I think I've got the
> > split pane widget 
> > working more or less correctly on both IE and Moz. The results are 
> > encouraging, although I've only been able to test w/ IE 6.0 
> > on Windoze. I'd 
> > consider the version in CVS to be at least as safe to use as 
> > the previous 
> > version of the widget and it is considerably better behaved 
> > in the common 
> > case now. If you have problems with the widget, please let me 
> > know about them 
> > (including widget file version and browser type and version).
> > 
> > Regards.
> > 
> > --
> > Alex Russell
> > [email protected]
> > [email protected]
> > 
> > _______________________________________________
> > The netWindows developers list: [email protected]
> > http://netwindows.org/mailman/listinfo/devel_netwindows.org
> > 
> > 
> 
> 
> _______________________________________________
> The netWindows developers list: [email protected] 
> http://netwindows.org/mailman/listinfo/devel_netwindows.org
> 
> 


_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org