The thing is - there's nothing wrong with the Singleton implementation, it
works just fine in my app (and inside modules). But when a module loads
another module, it stops behaving as a Singleton.
So it seems like a Flex bug ?
On 06/12/2007, bjorn - [EMAIL PROTECTED] wrote:
Thanks for
Thanks for the link, I'll check it out (but I'm from a Java world so I like
my .getInstance() ;-) )
Here's my singleton test implementation:
package com.juicability.moduletesting
{
public class TestSingleton
{
private static var instance:TestSingleton; // the only instance of this
I've found using Darron Schall's singleton implementation seems to
work great for my projects.
http://www.darronschall.com/weblog/archives/000274.cfm
Short of that can you post your singleton implementation code (or at
least the constructor) ?
--- In flexcoders@yahoogroups.com, bjorn -
gah, of course, I meant to say singletons and modules in the subject!
Sorry about that :-|
On 05/12/2007, bjorn - [EMAIL PROTECTED] wrote:
I've made a simple testcase with a singleton and three Flex projects:
1. MainApp
2. ModuleOne
3. ModuleTwo
MainApp loads ModuleOne which loads
4 matches
Mail list logo
