can't send notification during local storage space request modal window open

[GoogleCodeExporter]

*What steps will reproduce the problem?*
1. Requesting space in local storage (pending status of SharedObject)
2. Sending a notification before User accepts or denies the request.

*What is the expected output? What do you see instead?*
I expected a notification sent to viewComponent's mediator, to alter view and 
show a message to user explaining why I ask for room in storage.
*instead*
[Fault] exception, information=TypeError: Error #1009:
(error saying that flash can't access property/method of null object)

*What version of the product are you using? On what operating system?*
Fabrication 0.8.2 - as3
PureMVC AS3 Multicore 1.0.5
Pipes 1.1
Flash Player 10.0
FlashDevelop 3.2.2
Windows XP

*Please provide any additional information below.*
I don't even know if this is a bug, but as it forces me to keep a reference to 
main class in my proxy and modify it from there instead of using it's mediator, 
and because I was lucky with finding a bug last time, thought that I will leave 
it here...

Thanks for Your great work, by the way :)

Original issue reported on code.google.com by [email protected] on 23 Jan 2011 at 8:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

here's an example:

var so:SharedObject = SharedObject.getLocal('test');
var flushStatus:String = null;

flushStatus = so.flush(999999999999);

if (flushStatus == SharedObjectFlushStatus.PENDING)
{
    sendNotification('test');
}

Original comment by [email protected] on 23 Jan 2011 at 9:00

[GoogleCodeExporter]

Hi,

Can you send me both proxy and mediator code ( zip file would be great ). Is 
there possibility to have whole stackTrace here, not just simple error 
description?

Cheers,
Rafał

Original comment by [email protected] on 24 Jan 2011 at 12:44

[GoogleCodeExporter]

I was expecting an answer like "it is normal You can't access some things when 
the modal windows is opened". Because that's not the case I made a simple app 
reproducing the bug (great way to find the solution btw) and realized the 
problem was in different place, so I'm terribly sorry but this time it's just 
me :(.

Original comment by [email protected] on 24 Jan 2011 at 2:18