This content has been marked as final. Show 4 replies
air.EncryptedLocalStore.setItem() and .getItem() ?
that will work. but surely that is overkill for what should be a trivial task.
Yes, using the encrypted local store for this is a bad idea. If nothing else, it's horrendously slow for this purpose.
This question is not actually about windows, as variables are not accessed from windows. Variables are accessed from code and are accessible/not accessible based on the visibility of their definition in the code.
For example, if two windows are using the same instance of an object then they can both see "foo" if foo is an instance variable of that object. If the two windows don't have any variables in common, then you could make "foo" global. If you don't want to make it global, you could attach it to some other variable that both windows have access to. Or, the code that creates the child window can explicitly pass this value to the code that runs on behalf of the child window, perhaps by setting a property. You could sub-class NativeWindow to add this property. And so on...
hope that helps,
Oliver Goldman | Adobe AIR Engineering
That helps a lot Oliver. Thanks for the reply.