Four Js Customer Forum

We've been struggling this for quite some time ever since GDC 3.10 upgrade.  It's getting better in GDC 3.20 to allow us to right-click on a web component and select "Open inspector in new window" to bring up the Chrome DevTool.  While it's good to be able to inspect elements and debug some JavaScript functions after the web component has been loaded, we cannot find any way to start JavaScript debugging in any of the gICAPI interface -- gICAPI.onData() for instance. 

In a situation where we need to debug the gICAPI interface, we have been resorting to use GBC running in a browser instead.  In this particular situation, we are having a consistency issue between GBC and GDC, so we really need to debug this while the application is running in GDC.  Anyone has any idea?

Hi Huy, yeah thats really annoying.
What you could do for now is having 2 js onData functions, the 1st is called while you have no chance to debug and just saves the data in a local js array, the 2nd is your "real" onData function.
If you are in the debugger you call a helper function (in this sample evalData()) to switch between both and feed the saved data to your real function.

var mydata=[];
...
function saveData(data) {
  mylog("gICAPI.saveData:"+data);
  mydata.push(data);
}

function realOnData(data) {
  mylog("gICAPI.onData:"+data);
  input.value=data;
}
//call this in the console once you are in the debugger
function evalData() {
  gICAPI.onData=realOnData;
  for (var i=0;i<mydata.length;i++) {
    realOnData(mydata[i]);
  }
}
...
onICHostReady =function(version) {
  ...
   gICAPI.onData=saveData;
}

I will register a request for easier debugging of the initial calls tomorrow.
HTH and Regards, Leo

Hi Huy, I registered GDC-04337,
"Have a convenient way to debug the initial phase of a webcomponent".
Could you make use of my technique ?

Thanks for the suggestion Leo.  That's what I usually have to do if I wanted to debug the onData() block: save data, then execute the data later using the debug console.