Comments on: Using (Native)Windows with AIR http://pegolon.wordpress.com/2008/03/18/using-nativewindows-with-air/ Developing software using agile techniques Thu, 29 Oct 2009 23:07:20 +0000 http://wordpress.com/ hourly 1 By: Vtrinity http://pegolon.wordpress.com/2008/03/18/using-nativewindows-with-air/#comment-276 Vtrinity Wed, 22 Apr 2009 16:20:30 +0000 http://pegolon.wordpress.com/?p=26#comment-276 Thanks for your reply. Can you please elaborate a little more. I would like to give you some more details about my application. I have WindowedApplication(Main App ) with custom chrome and there are dividebox, canvas, hbox containers within it. I add the components from mx:window to the containers inside the main app and vice versa. And I see that tooltips, comboboxes do not come on the mx:windows but rather on the main app. I appreciate your response and look forward for some more.. Vandana Thanks for your reply.

Can you please elaborate a little more.
I would like to give you some more details about my application. I have WindowedApplication(Main App ) with custom chrome and there are dividebox, canvas, hbox containers within it. I add the components from mx:window to the containers inside the main app and vice versa. And I see that tooltips, comboboxes do not come on the mx:windows but rather on the main app.
I appreciate your response and look forward for some more..

Vandana

]]> By: pegolon http://pegolon.wordpress.com/2008/03/18/using-nativewindows-with-air/#comment-275 pegolon Wed, 22 Apr 2009 04:50:59 +0000 http://pegolon.wordpress.com/?p=26#comment-275 I remember having the same problem. It is the PopupManager who is responsible for this behaviour. You could use one whole-screen native window with transparent chrome and put the other windows as Canvas in them. The user doesn't feel the difference. Hopes this helps. Markus I remember having the same problem. It is the PopupManager who is responsible for this behaviour. You could use one whole-screen native window with transparent chrome and put the other windows as Canvas in them. The user doesn’t feel the difference.
Hopes this helps.
Markus

]]> By: Vtrinity http://pegolon.wordpress.com/2008/03/18/using-nativewindows-with-air/#comment-273 Vtrinity Tue, 21 Apr 2009 22:22:14 +0000 http://pegolon.wordpress.com/?p=26#comment-273 Hi, This is with respect to AIR windowing system. I am working on an application where components have to added/ removed from the main application window and added to new windows. The issue I am facing is with Comboboxes, tooltips all show up in the main application window rather than the popped up window. I am using mx:Windows and mx:WindowedApplication. Please let me know If you have any thought about it. Thanks & Regards Vandana Hi,

This is with respect to AIR windowing system. I am working on an application where components have to added/ removed from the main application window and added to new windows.
The issue I am facing is with Comboboxes, tooltips all show up in the main application window rather than the popped up window. I am using mx:Windows and mx:WindowedApplication.
Please let me know If you have any thought about it.

Thanks & Regards
Vandana

]]> By: Chad http://pegolon.wordpress.com/2008/03/18/using-nativewindows-with-air/#comment-107 Chad Thu, 22 May 2008 17:33:26 +0000 http://pegolon.wordpress.com/?p=26#comment-107 Hello, very useful advice. I wonder if you could expand, so if we want to use Flex Components we can create a separate MXML window and initialize that instance of a window or my making it through var window:Window = new Window(); When would we want to use a NativeWindow instead of an MX/Flex Window? Is better just to use a MX/Flex Window to be on the safeside and to prevent running into buggy situations? Another problem I have ran into is following the event handling for NativeWindowBoundsEvent.MOVE for the main /first window "WindowedApplication", because the WindowedApplication is an MX/Flex Window (Can contain Flex Components). I've tried this.nativeWindow for attaching the event, no go. Thanks, Chad Hello,

very useful advice. I wonder if you could expand, so if we want to use Flex Components we can create a separate MXML window and initialize that instance of a window or my making it through var window:Window = new Window();

When would we want to use a NativeWindow instead of an MX/Flex Window? Is better just to use a MX/Flex Window to be on the safeside and to prevent running into buggy situations?

Another problem I have ran into is following the event handling for NativeWindowBoundsEvent.MOVE for the main /first window “WindowedApplication”, because the WindowedApplication is an MX/Flex Window (Can contain Flex Components). I’ve tried this.nativeWindow for attaching the event, no go.

Thanks,

Chad

]]>