Jan M

if I create a Global object inside a [js] and add some properties I can read them as expected i.e with 

var testGlobal = new Global("foobar");
testGlobal.foo = 1.2;
testGlobal.bar = function() {
   post("something \n");
}


will return the property names correctly within the same [js] as the Global was created.

However, if I create another Global("foobar") within another [js] instance I can call the properties (they behave as public props) but they won't be listed (behave like private props). Does anyone know why this is happening? Is there a workaround?

if I create a Global object inside a [js] and add some properties I can read them as expected i.e with getOwnPropertyNames or for/in

reading-properties-of-global-instance-from-second-js-instance

@JAN - did you ever get an answer on this? thanks!

@JAN - did you ever get an answer on this?   thanks!


support wrote me back then. It's simply not implemented in the Global object. I wrote a small event listener/subscriber to notify other js instances about changes: 

https://cycling74.com/tools/jm-event-javascript-events/#.VzmUn8uxVAg

Hi DRKOSS,
support wrote me back then. It's simply not implemented in the Global object. I wrote a small event listener/subscriber to notify other js instances about changes:  https://cycling74.com/tools/jm-event-javascript-events/#.VzmUn8uxVAg

@JAN - thanks for the reply. I'll check out your listener for sure.

@JAN - thanks for the reply.  I'll check out your listener for sure.


Reading properties of Global instance from second [js] instance