Accessibility

Central Release Notes

AOL® Instant Messenger™ (AIM®) SDK 1.0 for Macromedia Central Release Notes

This document addresses issues not discussed in the AOL® Instant Messenger™ (AIM®) for Macromedia Central documentation. This document may be updated as more information becomes available.

About the AOL Instant Messenger SDK for Macromedia Central

The AOL Instant Messenger SDK for Macromedia Central contains tools, components, documentation and other resources for developing AOL Messaging applications for Central.

AIM client for Central

The AIM service is provided by a set of servers available on the Internet. An AIM client for Central is a Central application that uses the AOL Messaging Agent to connect to the AIM service. These servers allow AIM clients to perform the following tasks:

  • Exchange messages with other AIM clients
  • Determine the presence of other users
  • Store Buddy Lists, Block Lists, and Allow Lists

ICQ client for Central

The ICQ service is similar to the AIM service, but instead of screen names, ICQ users are identified by an ICQ number. These numbers are represented as character strings in the AOL Messaging environment. For example, the ICQ number 12345678 is represented as the character string "12345678".

Most of the documentation for the AOL Messaging environment focuses on the AIM service, but the concepts apply also to ICQ. Certain methods have special parameters that apply only to the ICQ service, and other parameters apply only to the AIM service.

About the AOL Instant Messaging Agent

The AOL Messaging Agent can access all of the AIM and ICQ services. The AOL Messaging Agent does not have its own user interface. The AOL Messaging Agent maintains lists of buddies and conversations that allow multiple Central applications and pods to communicate with the AIM service through a single AIM session.

System Requirements

The AOL Messaging SDK requires the Central 1.5 SDK. The Central 1.5 SDK requires the Flash MX 2004 authoring environment, version 7.2 or higher, to support the new version 2 components. If you have Flash MX 2004 installed, and need to update to the latest release, download the Flash updater.

For information on system requirements for the Central client, see the Macromedia Central system requirements.

Extension Manager

The AOL Instant Messenger (AIM) for Macromedia Central SDK requires Extension Manager version 1.6 (installed with MX 2004) or later.

Version 1.6 installs with Macromedia Flash MX 2004, but if you need to update your version of the Extension Manager, you may download the Extension Manager from Macromedia Exchange.

Installing Macromedia Central extensions in the Macromedia Flash MX 2004 authoring environment

Note: Uninstall any previous versions of the AOL Instant Messenger (AIM) for Macromedia Central SDK before installing the latest version.

To install Macromedia Central extensions into the Flash MX 2004 authoring environment, open the Extension Manager and explicitly select "Flash MX 2004 " as the installation environment, by following these steps:

  1. Open the Extension Manager.
  2. Select Flash MX 2004 from the pop-up menu.
  3. Select File > Install Extension, and navigate to the location where you have unzipped the MXP file (for example, C:\Central AOL Messaging SDK\CentralAOL.mxp).

Issues for Both Windows and Macintosh

The following lists known issues with AOL Instant Messenger (AIM) for Macromedia Central development on both Windows and Macintosh operating systems:

AIM client for Central


Rapid reloading of Buddy List disables the tree

Quickly reloading the Buddy List pod (clicking "Buddy List" in the pod dropdown in succession) disables the ability to close and open groups on the tree. Users can resolve this by closing and reopening the console.

The warn context menu in the Chat Pod does not function
To warn a buddy, open the main application window and click the 'Warn' button from within that buddy's conversation tab.

Checkbox in Sign On dialog box may disappear
After selecting then un-selecting the save password checkbox in the AIM Sign On dialog box, the checkbox will be disabled. To re-enable the checkbox, type a character in the Password field, or close and reopen the dialog.

No scroll wheel functionality in Buddy List Setup
Mouse scroll wheel does not function in the Buddy List Setup's Buddy List.

No tab sequence from AIM application to Central toolbar
Users are unable to tab in to the Central toolbar controls from within the AIM application.

ICQ client for Central


ICQ does not automatically limit characters

When opening a new conversation panel, ICQ does not limit the number of characters you can type. You can try to send messages of any length, but the send operation will fail if the message is longer than 800 characters for online contacts, or longer than 450 characters for offline contacts.

AOL user details button incorrectly enabled
Sometimes, the user details button is enabled for AOL users, resulting in a broken link.

No Keyboard navigation in Add User dialog box.
Keyboard navigation does not work in the Add User dialog box.

Setup window contact renaming terminates
When renaming contacts in the setup window, clicking inside the edited item terminates the editing action.

AIM messaging agent


May require multiple sign on attempts

After signing on to Central on one machine, then on another machine, and then again on the first one (all with the same screen name), may require a couple attempts to sign on.

User detection between clients occasionally inaccurate
ICQ users may appear offline to AIM users and vice versa. Also, OnBuddyStatusChanged may not be called in AIM when an ICQ buddy status changes.

Going online with Central may require a restart to sign on to AIM
If Central is launched offline, and then connected to the Internet while still open; then you will have to restart Central before you can sign on to AIM.

Group renaming requires setup
You will not be able to rename a group by merely changing the letter casing.

No error message if an SMS recipient is invalid
If you send an SMS to an invalid number, you will not receive an error.

HTML formatting end point
HTML formatting in IM messages received from AIM for Windows may not always end at the designated spot.

HTML formatting clean-up limitations
CleanInboundHTML does not convert a font size greater than 7. Also, CleanInboundHTML and cleanOutboundHTML do not convert decimal font sizes accurately.

AIM Service only


Chat room rate limiting is not implemented

The onChatRateLimitedChanged call in IAIMClient is never called. Instead, if you send too many messages too quickly to a group chat room, you will be ejected from it.

Need to use answerInvitation_R to enter a chat room in response to an invitation
You cannot enter a chat room that you have been invited to via a call to enterChatRoom_R. You must instead use answerInvitation_R

Cannot re-enter a chat room under the same name
After being in a chat room called “blue room” and closing Central, you will not be able to enter the chat room with that name again. You will, however, be able to enter that room again if you use different white space variations, such as “blueroom” or “b lue room.”

First message is a "knock-knock"
After adding a buddy to your buddy list, the first message received from that buddy will be a knock-knock.

Cannot reset a buddy if no alias exists
If no alias is set for a buddy and you try to reset it again (i.e. set it to an empty string) you will get an error.

replaceBuddyInGroup_R cannot handle non-numeric aliases
If you pass an alias for a non-numeric buddy to replaceBuddyInGroup_R, you will not get an error.

Declining an invitation timeout
If a buddy waits too long before declining a chat invitation, you may not receive an onSentInvitationDeclined event.

Cannot set Recent Buddies collapsed state
You will not be able to set the collapsed state of the Recent Buddies group.

BuddyArtChanged may not be called properly
When a buddy changes his or her wallpaper, on BuddyArtChanged may not be called.

ICQ Service only


onBuddyStatusChanged

onBuddyStatusChanged may not always be called for a buddy returning from being away. Also, onBuddyStatusChanged may return an empty object when your privacy mode is set to ALLOW_IN_LIST and that buddy is not in your allow list.

getBuddyInfo_R does not return certain properties
getBuddyInfo_R does not return values for the following oICQInfo properties: sAge, nGender, sEmail.

closeConversation_Result not called
closeConversation_Result does not get called.

Buddy search by city may not function
doBuddySearch_R does not return any results when searching via the sCity parameter.

User status may be unavailable depending on Web Aware settings
The status returned in search results is only online or offline and may be unavailable, depending on the Web Aware preference of the found user.

High ASCII characters may not display
High ASCII characters returned in search results may not display correctly.

User status not preserved after signing off and back on
After setting your status or privacy, then signing off and back on, your status will be available and the privacy mode will be ‘ALLOW_ALL’. (Normally ICQ clients preserve your status when you sign back on.)

Moving buddy error
You may get an error when trying to move a buddy that is pending or that has an alias set.

Long away messages may not work
If a buddy sends you an IM while you have a long away message (500 or more characters), that buddy may not get an auto-response with your away message.

Your own away status for signed-on user may be incorrect
When calling getBuddyInfo_R for the signed on user while away, the status returned may be available unless you are on your own buddy list.

Does not correctly report multiple sign on
ICQ does not report correctly a situation where you are kicked offline because your ICQ# has logged on elsewhere. All you receive is a message that you are offline.

No away messages received from Windows ICQ clients
ICQ does not receive away messages from Windows ICQ clients. Away messages are received only from MacICQ and Central ICQ.

Reporting a Bug to the Macromedia Central Team

Found a bug? You can contact Macromedia Technical Support. They can help you resolve issues; and they can also log bugs. You can also file a bug yourself by using the Macromedia Software Feature Request and Bug Report form.

Note: Due to the high volume of e-mail we receive, we are unable to respond to every request.

Thank you for using Macromedia Central, and for taking the time to send us your feedback!

Notices, Terms, Conditions, and Attribution

Copyright (c) 2004 Macromedia, Inc. and its licensors. All rights reserved. Macromedia, the Macromedia logo, Central, Macromedia Central, Flash, Macromedia Flash are trademarks or registered trademarks of Macromedia, Inc. in the United States and/or other countries. Other marks are the properties of their respective owners.

This computer program is protected by copyright law and international treaties. Unauthorized use, reproduction, or distribution of this program, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law.