Solution can't see globals.js file

Classic Servoy
1

In going through the process of fixing broken functions in moving from 3.5 to 5.2 things really got fowled up.

I suddenly lost all global methods from my active solution module. I restored the workspace to before the problem, and the globals.js is in the workspace file and the file appears to have all the functions. Similarly, I can open up the globals.js file in 5.2, but the solution explorer can’t see them. All other modules can see their globals methods.

Is there a way to repoint the module to the workspace file?

Right now the solution is totally broken and any help would be greatly appreciated.

Thanks for your help. K

2

Hi kurtbleicken

I suffered the same problem. The cause was an error in one method inside the globals.js file. To make it visible again I fix the corrupted method and everything went well again.

To see the globals.js file use the navigator [Window → Show View → Other → Navigator], double-click and edit it.

Best regards. Roberto.

3

i am very interested in the contents of that global method (you can open it through the navigator just fine)
It seems that you have a parsing problem. It could be just a real typo or something the parser should handle a bit better.

4

Thanks Roberto,

Indeed there was an error in the globals.js file. I think I had commented out a section of a function and there was a tiny red dot next to the */ Once I fixed that suddenly all the active solution globals suddenly appeared. Weird? K

5

A while ago I had the same problem and it was caused because of the following:

I’m using a XML plugin and I used the following script:

var x = oElement.CDATA

That caused also that I couldn’t see the contents of my globals.

I changed this line to:

var x = oElement['CDATA']

and the problem was solved.

The problem was the CDATA word.