Starting July 1st, the Georgia Virtual School will switch from using Elluminate Live! Adobe Connect requires client systems to communicate on port 1935. Mac OS X v10.4–10.6 (Intel); Mac OS X v10.4 (PowerPC). Android™ devices: Android 2.2; Adobe AIR® for Android; compatible with HTC Nexus One. For some reason trace does not work on when I put trace into my ActionScript files. I use the Flex SDK to build Adobe Air applications. I am currently on Flex SDK 4.5.1 and Adobe Air 2.7. Starting July 1st, the Georgia Virtual School will switch from using Elluminate Live! To Adobe Connect for online synchronous classroom communications. Adobe Connect requires client systems to communicate on port 1935. Adobe has an online test available at for client system testing. The following lists the technical requirements for all supported client systems. NOTE The standard chrome is managed by the operating system, and your application has no direct access to the controls themselves. You can, however, react to the events that are dispatched as a result of the user interacting with these controls. (See “Understanding Window Events” later in this chapter.) NativeWindowSystemChrome.NONE This option specifies that the window should not display any system chrome whatsoever. Creating a NativeWindow with no chrome generates a rectangle onscreen with no controls. This is the starting point for implementing custom chrome discussed later in this chapter. The following demonstrates how to specify no system chrome: var windowOptions:NativeWindowInitOptions = new NativeWindowInitOptions(); windowOptions.systemChrome = NativeWindowSystemChrome.NONE; NativeWindowInitOptions.type Each window offers unique traits suited for different roles in an application. There are three NativeWindowTypes to choose from: • NORMAL • UTILITY • LIGHTWEIGHT NativeWindowType.NORMAL This is the default window type. If nothing is specified for this parameter in your NativeWindowInitOptions, shows what is displayed. NOTE There are applications that utilize this window type as its primary user interface. These are typically smaller, more specialized applications such as instant messaging or media players. There isn’t a need to crowd the user’s Dock or taskbar with an application running in the background most of the time. NativeWindowType.LIGHTWEIGHT LIGHTWEIGHT NativeWindows have no chrome whatsoever. In fact, you’ll get a runtime error unless you specifically set the systemChrome property to NONE. Creating a window in this fashion gives you a white box that can’t be moved or even closed directly. Demonstrates a native window with no chrome and uses a bitmap image as the window’s background. An Adobe AIR application implemented with custom window chrome. ![]() Uses for LIGHTWEIGHT NativeWindows range from custom system chrome implementations to toast messages (dialogs that temporarily slide up onscreen like toast out of a toaster) to drawer dialogs common on Mac OS X. NativeWindowInitOptions.transparent This property refers to the transparency of the window background window. A transparent window has no default background. Any area not occupied by a display object is invisible; for example, whatever lies beneath your application window shows through. You can also change the alpha property of your display objects to allow underlying desktop content to show through. NOTE As with the NativeWindowInitOptions.maximizable property, on Mac OS X, you’ll have to set both the maximizable and resizable options to false to prevent the window from being zoomed or resized. Creating an Instance of the Window Now we need to create a new NativeWindow instance. Remember that the properties defined in NativeWindowInitOptions cannot be changed after we instantiate the window. The default window size is determined by the operating system, but you can change it by setting the window bounds. (We’ll look at this later in the chapter.) var newWindow:NativeWindow = new NativeWindow( windowOptions ); The variable windowOptions refers to the NativeWindowInitOptions we constructed in the previous section. Putting the Window Onscreen If we were to stop at the previous step, the user would not see anything appear onscreen. After instantiating our NativeWindow, we need to specifically put it on the screen. ![]() There are two ways this can be accomplished: NativeWindow.activate() or NativeWindow.visible = true Using NativeWindow.activate() Invoking the activate() method on the NativeWindow instance does the following: • Makes the window visible • Brings the window to the front • Gives the window keyboard and mouse focus The following snippet instantiates a new NativeWindow, passing in window options, followed by the activate() method. Var newWindow:NativeWindow = new NativeWindow( windowOptions ); newWindow.activate(); Using NativeWindow.visible This property specifies whether the window is visible on the desktop. It affects only visibility and does not give the window focus or bring it to the front. For example, you might want to open a supporting UTILITY type window for an application where focus must remain on the primary window. Rather than activating your window, simply set its visible property to true, and it appears onscreen without the primary window flashing in and out of focus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2019
Categories |