Adobe AIR Non-Transparent Window Bugs Part 3: Native Controls Showing Up

In my previous post, I showed how sometimes Windows would draw native controls on top of your non-transparent windows, as pictured here: However, I could not figure out a sure way to reproduce it. Now I have. Here's how you do it: 1. Make a new AIR application in Flex Builder. 2. In your-app.xml, set systemChrome to none [...]

You Might Also Like...

  • Tile Options Demo using Flex 4

    616 readersIn a previous post, I showed a demo of a custom list component created with Degrafa.  I received a request for the same application done with Flex 4 and FXG, so I spent a little time converting it over and here is the result. (** requires Flash Player 10)  I’m sure I could have used

  • Flex 4 Smoked Glass Container Skin

    705 readersOn a project I’m working on, I need to have semi-transparent containers to hold controls over top of screen-filling bright and colorful background. While I’m not 100% satisfied with it, I think it will suffice for the time being. I was originally going for an effect similar to the window borders in Windows 7 where

  • Invoking the Flex Compiler via Native Process API in AIR 2.0

    985 readersAIR 2.0 comes with the ability to interact with native processes. This means we can launch a process from the AIR application and communicate with its standard input/output. However, applications using the native process api must be packaged into native installer. Therefore, you must compile it separately in Windows, Mac and Linux to get 3

  • Flex Spark application background alpha

    1124 readersSometimes when creating a web based Flex application you want the background to be transparent or semi-transparent. In Flex 3 this involved two steps, setting the 'backgroundGradientAlphas' property on the mx:Application to [0,0] or something less than 1 and setting the 'wmode' on the swf to 'transparent'. Now with Flex 4 (Spark) it's not quite

  • Creating three related Spark DropDownList controls in Flex 4

    1109 readersIn a previous example, “Creating two related ComboBoxes”, we saw how you could create two or three related MX ComboBox controls in Flex 3 by binding to the previous ComboBox control’s selected item. The following example shows how you can create three related Spark DropDownList controls in Flex 4 by using databinding and XML. <?xml

  • AIR for Android trace() with logcat

    397 readersIn my previous post I talked about how to use Flash Builder 4 to debug an AIR application running on an Android device. In this post I will show a poor man's way of getting trace statements. You have to build the application with debug mode and apk-debug target packaging. Then before you run the

  • Creating a Flash Professional Android Project

    305 readersThis post and it’s brother Creating a Flash Builder Android Project are going to be really short and sweet. I just want to make sure that there are no places for questions. If you are starting with this post I recommend actually starting with a previous post introducing AIR for Android Development. There is a

  • Important Development Workflow Change in AIR 2

    4044 readersIf you're an AIR application developer, and you tend to run an installed version of an application at the same time that you're developing it, this post contains important information on how your development workflow will need to change for AIR 2. In AIR 1.5.3, we made some changes to the way that AIR files are

  • SimTouch – Simulate Native TouchEvents on the Flash Platform

    524 readersSo, I promised SimTouch would be good to go by March 1st and here it is in all it's 'beta' glory. SimTouch is an Adobe Air application that simulates native touch events on the Flash platform. SimTouch is a transparent app that sits on top of the application that you are developing and dispatches TouchEvents

  • Quickly Build Native Installers for Adobe AIR 2

    3228 readersAdobe platform evangelist Serge Jespers released on his blog a valuable AIR 2 "alpha" application that allows you to quickly build native application installers for your AIR 2 applications. Native installers are required if you are building an AIR 2 application that takes advantage of the new extensibility options available from the native process