MOTODEV Studio for Android Release Notes

MOTODEV Studio for Android Installation and Update Issues

• After upgrading to MOTODEV Studio for Android version 3.1, there may seem to be fewer snippets (in the Snippets view) than before. This is due to an issue with the Snippets search box: it remembers the last search and only shows the matching results, even though the search box is now empty. To resolve this issue, simply enter some text into the Snippets search box ("GPS", for instance) and then erase it; this restores the full list of snippets.
• There is a known bug regarding SDK tools and Proguard that requires you to manually update the Proguard library (located under SDK_PATH/tools/proguard/lib) to version 4.6 or higher.
• Because MOTODEV Studio version 3.0 is based upon Eclipse 3.7 (Indigo), if you are currently running MOTODEV Studio on an earlier Eclipse version (such as Helios) you must upgrade to Eclipse Indigo prior to installing MOTODEV Studio 3.0 from the archive.
• To avoid SWT-GTK bug 345979, developers running Eclipse with the MOTODEV Studio plugins on Ubuntu 11.04 may want to create an Eclipse launch script like the following in their Eclipse installation folder:
  

  #!/bin/sh
  unset UBUNTU_MENUPROXY
  export LIBOVERLAY_SCROLLBAR=0
  ./eclipse
  

• Beginning with MOTODEV Studio version 3.0, Motorola Mobility no longer produces a 32-bit version of MOTODEV Studio for Mac OS X. If your development computer runs Mac OS X, either install the 64-bit version or install Eclipse and the MOTODEV Studio plugins.
• If you try to authenticate using the p2 framework and the authentication fails, the login dialog is opened twice more. Then, an error message is displayed indicating that authentication has failed. If you immediately try to re-authenticate, the error message may be displayed without the login dialog. Restart MOTODEV Studio to work around this issue.
• Sometimes when downloading the Android SDK using MOTODEV > Download components, the download job might not finish correctly and subsequently the "Download components" dialog may malfunction. Either wait a short period for the job to finish, or kill the MOTODEV Studio process and start it again.
• The Linux install was tested on Ubuntu with the OpenJDK VM. While the Linux install has not yet been tested with the Sun VM 1.6b24, this configuration may work.
• On at least one occasion the Linux uninstaller was seen to stop working. If this happens to you, simply kill the uninstallation process and manually delete the MOTODEV Studio for Android folder.
• On Microsoft Windows, the Add SDK folder to the system path option (available when downloading or selecting an SDK from the Download Components dialog) may not take effect until Windows is restarted. Accordingly, you may want to reboot your computer after downloading or selecting an Android SDK.
• (Version 3.0 only) If you get an error when clicking the Download platforms, non-Motorola add-ons and samples link in the Download Components dialog after downloading the Android SDK, dismiss the error and click OK to exit the Download Components dialog. MOTODEV Studio will automatically detect that you do not have any platforms and will offer to open the Android SDK and AVD Manager for you (which you can also do yourself by selecting Android SDK and AVD Manager from the Window menu).
• (Version 3.0 only) When using the Download Components dialog to install Motorola add-ons, you may notice that some add-ons are grayed-out and thus cannot be selected. Grayed-out add-ons are ones that require a platform that you have not yet installed. If you install the needed platform(s) by selecting SDK from the left pane and then following the Download platforms, non-Motorola add-ons and samples link, upon once again selecting Motorola Add-ons in the Download Components dialog the grayed-out add-ons will still be grayed-out. Click Refresh to properly update the list of add-ons.
• Because ProGuard doesn't like spaces in the paths to either your projects or the Android SDK, when specifying a location for the Android SDK be sure to choose one that will have no spaces in the path.
• When installing as plugins to an existing Eclipse, if you don't select MOTODEV Application Validator the Validator will still be installed, but due to an Eclipse P2 bug updates to it will not be detected. In order to receive all updates, select the MOTODEV Application Validator when installing MOTODEV Studio as plugins.
• When installing MOTODEV Studio for Android as plugins, note that you can install only on a compatible base product such as Eclipse Classic or Eclipse Pulsar. MOTODEV Studio for Android plugins cannot be installed into an existing MOTODEV Studio.
• Before installing MOTODEV Studio for Android as plugins to an existing Eclipse installation, if you have an older version of Google's ADT plugin installed, uninstall it. The MOTODEV Studio for Android plugins install the latest ADT from Google, and an existing installation of an earlier version is likely to conflict.
• On Windows 7, MOTODEV Studio (and Eclipse by itself) may stop working or crash when trying to restart itself (after installing something, for example). If this happens, close and start MOTODEV Studio (or Eclipse) again manually.
• The MOTODEV Studio for Android installer determines which (if any) JVM is installed on your computer. If it finds more than one, it displays to the user only the first one found, which may or may not be the one that is actually used by MOTODEV Studio. Note that you must have installed (and MOTODEV Studio must use) the correct JVM for your processor architecture (32-bit or 64-bit) or you will experience errors in Eclipse/MOTODEV Studio.
• On Linux hosts, after installation the desktop shortcut may appear with the wrong icon. This happens when the shortcut was created without execute permission. Either grant the shortcut execute permission, or try to launch MOTODEV Studio for Android using the shortcut and, if asked, indicate that you trust the shortcut.
• When updating the Android SDK on Microsoft Windows, you might see a message like the following:

  -= Warning! =- A folder failed to be renamed or moved. On Windows this typically means that a program is using that folder (for example Windows Explorer or your anti-virus software.) Please momentarily deactivate...

  The updater is trying to update the SDK in the MOTODEV Studio installation folder (although that may not be the SDK you thought you were updating). Delete the SDK in the MOTODEV Studio installation folder and then re-run the updater.
• If you are downloading new components/updates and an error occurs (because of network instability, for example), sometimes a corrupt file may remain in the cache. If this happens, any further attempt to download the same component will fail. If you are getting errors on all attempts to download components/updates, empty the contents of the installation_folder/p2/org.eclipse.equinox.p2.core/cache folder, then try to download again.

Project Creation Issues

• ProGuard doesn't like space characters in either your project path or the SDK path. This will manifest itself when creating a new project (if you select the Obfuscate Java classes option) or when you later enable obfuscation by altering the project's properties (select MOTODEV Studio from among the project's properties). When creating a new project, ensure that the complete path to that project contains no space characters.
• When creating a new Android project, if you clear the Use default location option you will be unable to specify a project location within your workspace. To create a project within the current workspace leave Use default location selected. Otherwise, specify a location outside of the current workspace.
• During project creation, if you specify a path in which the parent folder doesn’t exist, an error is displayed. For example, if you specify the path C:\temp\projects\myproject and the projects directory doesn’t exist, you will encounter this problem. Ensure that the project's parent folder exists before creating a project in it.
• In the New Project wizard, as you edit the Project Name field the Project Location field is automatically generated. Sometimes, this field is not generated as expected.
• If you install new packages using the AVD Manager and you then try to create a project, you may see no available targets. If this happens, reopen the AVD Manager (Window > Android SDK and AVD Manager) and then close it. The new project wizard should now work.
• If your project's name starts with a digit and you use the default package name created by the wizard, the generated APK will be invalid. When generating the default package name, the wizard replaces leading digits in the project name with a single underscore ("_") character; since individual package name parts must start with a letter, this results in an invalid package name. Either ensure that your project name doesn't begin with a digit, or alter the package name so that it is valid.

Localization Files Editor Issues

• If you try creating a building block using one of the wizards (such as the New Activity Wizard) while the Localization Files Editor is opened for the project and has not been saved (it is marked as dirty), synchronization problems with the localization files may cause the creation operation not to complete correctly. Therefore before you start to create new building blocks, either save your localization resources or close the Localization Files Editor.
• The Localization Files Editor on occasion leaves the "Highlight Changes" mark on a cell even after the file is saved.
• When editing multiple files with the Localization Files Editor, if you change a key and then use the Revert to Saved option, the old keys will be reloaded from the file but the new key name will remain, causing both the old key name and the new one to be shown.
• The first time you use the Localization Files Editor the text will be formatted. This can cause the editor to flag the text as having changed when you switch between the Android Localization Files Editor and values/strings.xml tabs.
• When “Highlight Changes” is enabled, cells that have only had their comments changed are not highlighted.
• Because the translation feature relies upon a third-party service to perform the text translation, there is no guarantee that HTML tags or end-of-line characters will be preserved in the translation. Always review the resulting strings to ensure that the translation is appropriate and that HTML tags and end-of-line characters are in the proper places.
• The Localization Files Editor does not validate HTML tags for consistency. Improper HTML tags will be noted at build time.
• &lt; and &gt; are unescaped in order to support HTML tags. For systems running Java 1.5, if you manually enter either of these as text, they will be unescaped to < and > respectively. This issue is fixed for Java 1.6.
• On Microsoft Windows hosts the "Expand Row Size" option may not take effect until you have closed and re-opened the Localization Files Editor.
• When "Expand Row Size" is enabled, all rows are sized to the height of the row with the tallest cell.
• If you move the mouse out of the comment window area while editing a comment, the comment window simply disappears.
• Undo/redo does not work for changes to comments.
• The Localization Files Editor does not notice when a file being edited is changed using an editor outside of MOTODEV Studio for Android (such as Notepad). It does notice when changes are made from another editor, such as a text editor or XML editor, within MOTODEV Studio.

Issues While Building, Installing, Running, or Debugging Apps

• MOTODEV Studio allows you to deploy an app to a device simply by dragging and dropping the app's APK file from either the Package Explorer or your operating system's file explorer to the target device in the Device Management view. On Windows 7 you cannot drag from the Windows Explorer if UAC is enabled. You can still drag and drop from Eclipse's Package Explorer, however.
• On occasion the Export Android Application feature reports an error regarding permissions on the dist folder. However, the apk file is successfully created.
• If you get a "permission denied" error when trying to run adb, ensure that adb has execute permissions set.
• On occasion DDMS displays messages such as "Fail to get adb version" or "Cannot execute program adb". Whatever the underlying issue, it does not seem to have any effect on MOTODEV Studio; these messages can safely be ignored.
• Occasionally, after exporting packages, the Install Application dialog may state that the package is "Unsigned or Malformed". Re-exporting the package solves the problem.
• If AndroidManifest.xml is open in an editor and has focus when you build your project, it may generate an empty AndroidManifest.out.xml file in your project, which then causes the build to fail. If this happens, you must delete AndroidManifest.out.xml and then ensure that another file (such as a Java source file) has focus in order to initiate a successful build.
• If you change SDKs while adb is running, adb is not killed. The running adb may not be compatible with your new SDK. If you experience problems after changing SDKs, manually kill the adb process. The correct adb for the new SDK will be automatically started when needed.
• If you suddenly start encountering compile errors in projects that were previously known to work (including newly imported projects that are known to build successfully), look at the project-specific settings for Java > Compiler and ensure that the compliance level is set to the correct value (generally, 1.6).
• If you try to install a package onto a device (real or emulated) with the “uninstall first” option selected, and you do not have the platform for that device in your SDK, an error will occur. You must either download the platform corresponding to that device, or manually uninstall the existing package from the device before installing the new one.
• When working with the 1.6 SDK, sometimes an error message appears when installing a package:

  Error executing the operation. Execution results: - exec '/system/bin/sh' failed: Bad address (14)

  If you try again, it should work.
• When running applications on a version 1.6 target, sometimes the following error occurs:

  Waiting 3 seconds before next attempt.
  ActivityManager: Error: Activityclass {XXX} does not exist.

  If you get this error, clean the project and re-run your application.
• If there is a handset and one or more AVDs online when you launch or debug an application using MOTODEV Studio for Android, you will be presented with the standard ADT device chooser dialog asking you to select a target device. Simply select the desired target again.
• If you use a method such as waitForDebugger() from the Android SDK's Debug class, when you run that application a new debug configuration will be automatically created and a debug session will start using this configuration. This new configuration will be listed among the other debug configurations, and can be used for subsequent debugging sessions.
• ADT may crash with a "null pointer" message if you try to run an application (either on the handset or on an emulator) while an emulator is starting. Avoid launching applications while emulators are starting.

Emulator Issues

• When an Android 4.0 Platform emulator or a Honeycomb emulator is started from within MOTODEV Studio—either from the Device Manager view or by using the Android AVD and SDK Manager—in some instances an error message is displayed indicating that the emulator process was interrupted and that it failed to allocate memory. This appears to happen only on 32-bit machines. If you experience this problem, you can do either of these:
  • Edit the emulator's properties and reduce the "Device ram size" to a smaller value (for instance, if it is currently 1GB change it to 512M).
  • Start the emulator via the command line (or using the Android AVD and SDK Manager from outside of MOTODEV Studio); upon launching MOTODEV Studio the running emulator will automatically be detected and attached to the Emulator view.
• With tools r12 the emulator's proxy option does not work correctly. If this is a problem for you, consider staying with tools r11 or switching to tools r13 instead.
• On Linux, with tools r12, the emulator has problems with the '-scale' parameter and may cause your emulator skin to turn black. If this is a problem for you, consider staying with tools r11 or switching to tools r13 instead.
• The AVD that ships with the Honeycomb SDK creates an emulated device with a very large display. Performance of this emulator image is known to be slow. We advise that you do not run the Honeycomb emulator image inside of MOTODEV Studio, but rather to run it as an external window. To do this, simply close the "Android Emulator" view inside MOTODEV Studio and do not allow it to be opened when you launch your emulator from the Device Manager view. Further, the first time you launch the Honeycomb emulator image, you should expect that it will not be accessible for 10-15 minutes while it unpacks its file system and performs initialization.
• When using VNC (as on a Mac), performance when using the Honeycomb emulator is very poor. For instance, it can take up to 30 seconds to respond to a drag event. MOTODEV recommends that you run the Honeycomb emulator outside of MOTODEV Studio.
• On occasion, using an emulator with a big screen (such as for Motorola XOOM™) on a Windows-based development computer causes a "phantom window" to appear in the taskbar. An entry for this window will appear in the Windows taskbar, but you won't be able to interact with it and you won't be able to see the window itself. This phantom window disappears when you stop the emulator and causes no other known side-effects.
• If you select Analyze Memory with MAT immediately after launching an emulator, you will be presented with an error because the emulator is not yet in a stable running state. Wait until the emulator is at a stable state before using the Analyze Memory with MAT option.
• On 64-bit Linux, using the latest Android SDK, when you try to quit the emulator it sometimes halts but the emulator window (or view, if the emulator is running within MOTODEV Studio) remains and the emulator process isn't killed. If this happens, use kill -9 to manually kill the process.
• MOTODEV Studio for Android does not support the emulator snapshot feature (which improves the emulator's startup time). To use this feature:
  • Use the AVD Manager to create and start emulators (enabling the snapshot option when creating).
  • To stop the emulator, detach it from MOTODEV Studio and then close the window. (To detach the emulator, simply close the Emulator view and specify that the emulator should not be killed).
  • If you prefer to use the Device Management view to start your emulators, specify the -snapshot and -snapstorage options.
• If you enabled your AVD to start from a snapshot in the Android SDK and AVD Manager, the Reset option in the Device Management view will not work. Before you can use Reset, you must disable the snapshot in Android SDK and AVD Manager.
• The "take screenshot" feature occasionally fails on Honeycomb; if this happens, simply try again.
• Due to a problem with the Froyo version of the adb daemon, having certain devices—such as Motorola CHARM™—plugged in to your Windows-based development computer can cause the emulator to become unstable. For instance, with CHARM plugged in you may find it hard to start an emulator instance or to perform many common operations such as app installation and uninstallation. This problem only occurs on computers running Microsoft Windows.
• When using VNC (as on a Mac), if you stop several emulators within a short time (or select multiple emulators and stop all of them using the toolbar's stop function), the Android Emulator view may freeze. If this happens, close and reopen the Android Emulator view.
• If you use the Device Management view's Language option to change the language used by the emulator and you neglect to choose a country, the Finish button will be enabled but won't do anything when you click it. Specify both a language and a country.
• On Linux, two errors occur when you close and reopen the emulator view without stopping the emulator:
  • The command sent by the Switch Layout button does not change the layout as expected. Instead, it is captured by Eclipse, which tries to launch an app using the most recently used launch configuration.
  • The visible area that was set before closing the view does not resize even if you zoom in or out.
• On some versions of Linux, when you close the Android Emulator view the running emulator is killed: you are not given the option to leave it running the background. MOTODEV Studio has a preference (MOTODEV Studio > Android Emulator) to deal with this. Clear the Show emulators externally upon closing the Emulator view option, and when you close the Android Emulator view the emulator will remain running (invisibly) in the background. Reopening the Android Emulator view will allow you to gain access to the running emulator once again.
• On occasion the Fit to Window option (in the Zoom menu) causes the emulator to blink. If you encounter this, change and restore the zoom level. For instance, zoom in and then zoom back out again.
• In some cases, the native solution used to present the Android emulator as a view within MOTODEV Studio fails to display the emulator in the open view. If this happens, either work with the emulator in an external window or select the Use VNC to show the Emulator within an Eclipse view option in the AVD's properties.
• If your Linux development computer has more than one display, note that the Android emulator must be on display 0. It crashes when you attempt to show it on other displays.
• On Linux hosts, in order to interact with the emulator using your host computer's keyboard the focus must be in the emulator tab. If you click the emulator screen itself, keyboard interaction will not work even though the focus appears to be there. Click on the tab (or in the view, which redirects the focus to the active tab) and then you can use your computer's keyboard.
• Within MOTODEV Studio, emulator device names are case-sensitive. If you start an emulator from the command line and the AVD name you supply doesn’t exactly match the device name shown in MOTODEV Studio, MOTODEV Studio will not recognize the running instance.
• The Other field in the Emulator Properties Startup Options is not validated in any way. In particular, if you supply the –avd option and specify an emulator instance other than the one that is to be launched, when you launch the emulator it will never complete the startup process. Ensure that any options you enter into this field are correct, and do not use the –avd option.
• On occasion the Android emulator stalls during start up. When launching the emulator for the first time the launch can take quite a while. If it takes more than ten minutes or so, however, the emulator has likely stalled. Stop the emulator and try again.
• If the emulator is not running when you launch or debug an application targeted to the emulator, MOTODEV Studio starts the emulator and deploys the application to it. On rare occasions, however, the emulator isn’t started and nothing seems to happen. This occurs when the emulator process is unable to connect to the ADB port. Although the emulator process is running, ADT does not recognize it and therefore neither does MOTODEV Studio for Android. Stop the emulator and try again.
• If you provide a timeout value that is too large, you'll see an error message that indicates that the value must be a positive integer. Provide a smaller timeout value.
• While the emulator is in use, your computer's CPU usage can reach a high value.
• The ADB shell console feature does not yet support commands such as CTRL-C to interrupt process execution. If the process that is executing depends on a command like this to stop, it cannot be stopped unless the ADB shell is killed, either by stopping the emulator, disconnecting the phone, or killing the ADB process controlling that shell.
• On rare occasions, when working with a single emulator instance and multiple ADB shells, an exception may be thrown when the emulator is stopped: “request rejected: device not found java.io.IOException: device (emulator-5556) request rejected: device not found”.
• On Mac OS X and on Linux, if you are having problems with the ADB shell feature it may be that the path to the Android SDK contains whitespace characters. If it does, move the SDK to an alternate location that has no spaces in the path and adjust the SDK Location field accordingly in the Android preferences.
• While quickly alternating between multiple emulators, you may see the following message: “Device rejected command: cannot bind socket java.io.IOException”.
• Sometimes the following error message is shown in the logcat view when stopping an emulator instance: “Stop request rejected: device not found”. This may occur because there are pending commands to be executed on the emulator, and the emulator was stopped before they could be executed.
• When using VNC to present the emulator within the Android Emulator view, MOTODEV Studio for Android ignores the scale startup option. Note that on Mac OS X the emulator is always presented using VNC.
• If you have two emulators running and the Emulator view is open using VNC, an operation selected from the context-sensitive menu may be performed on the wrong emulator instance (that is, it may be performed on the emulator that is not currently showing in the Emulator view). This occurs when you:
  

  Note that this is only an issue when using VNC to present the contents of the Android Emulator view (on Window and Linux, this is normally not a problem since the default is not to use VNC; on Mac OS X, VNC is the only option).

  1. Change the selected emulator from the Device Manager view.
  2. Without otherwise interacting with the Emulator view, right-click it and select an option from the menu that appears.

• In the Startup Options dialog for an Android Virtual Device, if you try to use http_proxy in Other Startup Options, your password and user name must not contain the characters '@' or ':'. Otherwise, MOTODEV Studio will not configure the emulator proxy properly. This happens because the command line for this property must follow the structure: http://username:password@proxyip:proxyport and MOTODEV Studio tries to parse this line using these characters as references.

MOTODEV Database Explorer Issues

• The DB perspective can't show a device's applications unless the device has been rooted and there is a superuser, since a normal user doesn't have access to the /data/data folder. Note that this restriction only applies to physical devices; emulated devices have no such issues.
• If you create a database and then immediately delete it, an error message will be displayed indicating that there was an error and that the file could not be removed.
• If you stop the emulator while browsing a database table on that emulator, the table editor is closed before you are asked to confirm whether the emulator should be stopped.
• Due to a Data Tools bug, when you add new lines to a table using the table editor, even if some of the fields have a default value the default values are not used.
• The MOTODEV Database perspective has an option to delete a database (right-click a database node and select Delete). In the case of a database located under the Workspace, only the connection profile is deleted: the database file itself is not. In order to delete the file, switch to the MOTODEV Studio for Android perspective and delete the file from the Package Explorer view.
• There is a bug in Data Tools that affects MOTODEV Studio: when loading SQLite databases it processes rows based only on the row typename instead of the row typeCode. This prevents columns with size constraints from being detected by the table editor.
• The menu displayed when right-clicking a database node contains some options that are only applicable for the Data Tools perspective: they don’t work when using the MOTODEV Database perspective, and can create problems if used. The options that should be avoided are: Rename, Duplicate, and Save Offline.
• On some occasions with version 1.6 targets, the emulator crashes while loading databases.
• The MOTODEV Database Explorer does not refresh itself automatically: you must click Refresh to re-synchronize this view with the file system.
• On rare occasions, while working with a connected a handset, a “widget disposed” message is displayed while trying to save an edited value.
• If a table has a data type not supported by the table editor, an exception will be raised when the editor opens the table. For instance, this problem occurs with the IMAGES and VIDEOS tables from the com.android.providers.media application.
• BLOB fields are displayed as text, regardless of their contents.

Native (NDK) Development Issues

• Due to a CDT issue, automatic building is disabled for projects with native support. When exporting a package with native (NDK) support, you must manually build it before exporting.
• When doing native development, MOTODEV Studio for Android will only generate C classes from native function declarations that are within the public class with the same name as the Java file. Native function declarations in other classes within that same Java file are ignored.
• Immediately after adding native support to a project, on occasion the console window turns black. Simply change the Background color preference for the console (in Preferences, C/C++ > Build > Console) to any other color, and then change it back to white. Alternatively you can just stop and restart MOTODEV Studio for Android. This appears to be a CDT bug.
• If you select the checkbox to add native support to a project and click OK, and then click Cancel while it is calculating dependencies (before license or installation begins), you'll get an error message.

Other Issues

• In this release the parser for the Google Translate v2 API is preliminary. We plan to have an update soon that fully supports this API.
• The language packs included with MOTODEV Studio for Android are not complete: some of the text strings have yet to be translated. Accordingly, after installing a language pack and launching MOTODEV Studio in that language, some English text may still be visible in some of the MOTODEV Studio components.
• If you open a workspace created with a previous version of MOTODEV Studio for Android, you may be shown an error dialog stating that a particular view was not found. This is due to a change of view IDs in the 1.3 version. If this occurs, simply reset the perspective (select Reset Perspective from the Window menu).
• On Linux, in the Device Management view, if you click the down-arrow button for the last item in a list (for instance, to display the commands that can be used with the AVD at the bottom of the view), the selection is moved to the immediately preceding item, and the chosen command is applied to that item. This is particularly harmful if you select Delete, as the wrong AVD is deleted. Rather than using the down-arrow button, right-click the list item to display the context-sensitive menu for that device or AVD.
• If you run the Activity, Service, Broadcast Receiver, or Content Provider wizards while Manifest.xml is opened, a warning is shown ("No grammar constraints (DTD or XML schema) detected for the document") and all file content is highlighted. Close and reopen the manifest file to resolve this issue.
• When collecting log files (Help > Collect Log Files), if you specify a folder for which you do not have write access the error message that is displayed (“Cannot create zip file”) is somewhat misleading. Fix the folder permissions or choose a folder for which you do have write access.
• MOTODEV Studio for Android includes a mechanism that by default is used to store all passwords (such as your MOTODEV password). On Linux, if you want to improve the security of your passwords, disable this mechanism: from the MOTODEV Studio Preferences dialog select General > Security > Secure Storage. In the Master password providers section, deselect the Java Password Provider and select the UI Prompt provider (if it is not already selected).
• On Ubuntu hosts, sometimes the preview of the last snippet of the GPS group does not appear. A blank area appears instead.
• If a web page contains errors, for each error the Eclipse internal editor may cause an error dialog to appear asking if you want to debug the page. If the errors do not prevent the page from being rendered, you can answer “no” to each and the page will appear normally. If there are multiple errors, this can be somewhat annoying, however. Instead, you may want to alter your MOTODEV Studio preferences so that it renders such pages using an external web browser.

Created: July 24, 2009
Updated: January 13, 2012

ECCN 5D002.a: In accordance with United States Export Administration Regulations (EAR), and specifically the Commerce Control List (CCL), this item has been classified 5D002.a. Export or re-export of this commodity and compliance with the U.S. Export Administration Regulations is ultimately the responsibility of the exporter. For more detailed information related to export or re-export of this item, please consult the EAR at http://www.access.gpo.gov/bis/ear/ear_data.html.