Hi Cliff,

thanks for replying!
I found a workaround by hiding the app on startup and showing it later on via a Timer, if I did so
in the StartUpCommand it wouldn't work.
I will examine your examples to see what I did wrong.
 

Thanks and regards!
krille

Hi all,

I want to reposition my app on startup to the last saved window position. I used DesktopCitizen and looked at the source code, but I can't exactly figure out what is wrong.

My problem is, that when I call my RestoreWindowPositionCommand from StartUpCommand, the window seems to not be completely rendered, because nothing happens.
When I call RestoreWindowPositionCommand later on, everything works, but it's kind of ugly because the window "jumps" to the new location...

How can I achieve the same window positioning behaviour as with DesktopCitizen?

Thanks in advance!

  OMG!!
Can't believe I didn't check that...
I copied an existing mediator and forgot to change it's name - ouch!

Thanks a lot!

Hello Everybody,

I have a problem that I don't really understand and would be glad to receive some help 
I'd like to register 2 mediators to my app, both beeing responsible for different views (MXML components)
within the AIR app.

In the StartupCommand's execute method I do the following

:

var app:MemorizeAir = note.getBody() as MemorizeAir;

// register proxies
facade.registerProxy( new DatabaseProxy() );
facade.registerProxy( new PreferenceProxy() );
facade.registerProxy( new PracticeProxy() );

// register mediators
facade.registerMediator( new PracticeMediator( app.practiceScreen ) );
facade.registerMediator( new VocabularyMediator( app.vocabularyScreen ) );

So "app.practiceScreen" is a different component than "app.vocabularyScreen", and now after
digging around I found out that only the first of these mediators will listen for notifications,
in the case above its the PracticeMediator.

Why is that please and what would be the solution to my problem?

Thanks in advance and keep up the great work!