Comments on: Modules and singleton manager classes

By: Andrea Bresolin

Andrea Bresolin — Fri, 12 Mar 2010 22:36:56 +0000

Suresh is right. With modules you can have a module-wide singleton or an application-wide singleton depending on whether you import the singleton class also in the main application or not. I’ve written a post on my blog about this that demonstrates the different behaviors. You can check it at http://www.devahead.com/blog/2010/03/beware-of-singleton-in-flex-modules/

By: Suresh Nagar

Suresh Nagar — Fri, 04 Dec 2009 08:09:53 +0000

Hi Jelger,
i think there is more to it.
I have two modules and one GlobalModel (singleton class).
in both the modules i am calling getInstance of the GlobalModel and setting values to the model.
The changes do reflect in both the modules through global model only if i declare/instantiate the GlobalModel in main file. If i do not do that both modules share separate instances, infact, it gets reset when module is loaded second time.

By: Jelger Muylaert

Jelger Muylaert — Sat, 06 Jun 2009 00:07:50 +0000

By creating the dummy Managers, you ‘activate’ them at the beginning of your application. If you don’t ‘activate’ them soon enough, you get strange errors indeed.

By: Dennis

Dennis — Thu, 07 May 2009 11:37:37 +0000

Thank you Peter!

That was exactly what I need!

Regards,
Dennis

By: rconceiver

rconceiver — Fri, 20 Jun 2008 04:47:55 +0000

Thanks once again Peter…:)

I was facing the same issue. Initially I thought it is occurring because the last Module is not been unloaded properly. So i tried with unloadModule(). But it didn’t work.

Finally I got this solution! Thanks for that…

But can you help me understand why this issue occurs. Is there anything wrong with the Module Child or something else.

Awaiting for the reply.

rconceiver

By: Kaushik Datta

Kaushik Datta — Fri, 26 Oct 2007 15:06:32 +0000

Can you please post an example to show a ProgressBar while the Module SWF is getting loaded?

TIA

By: Valery

Valery — Tue, 07 Aug 2007 10:54:46 +0000

Interesting, I have some strange issue with modules and styles — probably should apply this workaround to StyleManager.

Btw, I’d prefer the following form of linking classes:

import mx.managers.PopUpManager;
import mx.managers.DragManager;

private static const LINKAGE:Array = [DragManager, PopUpManager];

First, you save a bit on characters typed. Second, you don’t pollute instance with unnecessary variables, so you save on object size and amount of scroll clicks during debugging ;)

Valery