リリースノート

Curl Development Tools for Eclipse (CDE) とCurl IDE 6.0.1005について

CDEはCurlのインストールディレクトリ / ide / eclipse-deploy にjarファイルとして配布されています。Eclipseのupdate manager機能を利用してこのプラグインをインストールします。詳細についてはインストレーションノートをご参照ください。

Curl CDE Installation note はこちら

以下が既に判明している問題です。

26578

For Pro license to take effect (when changed from the license dialog) you must restart the Curl RTE.

28782

Maximize the outline view results in a blank (empty) view.

28865

On Linux, some dialogs are not modal (e.g. the "Save Resource" dialog).

28935

When creating a Curl project outside of the workspace the path specified in the dialog is not fully validated.

28987

pc-line highlight background (pink) is not applied after step-into when the editor is reused for another source file.

29056

Manifest Explorer icons do not reflect source control status (checked out, etc.).

29084

A BOM in a file (incorrectly) overrides any curl-file-attributes encoding that may also be present.

29115

The Run | Toggle Method Breakpoint menu pick is not implemented.

29196

Breakpoints move to line 1 when file is reverted.
Workaround: Manually delete the breakpoint, and reset breakpoints as needed.

29204

Navigate menu item "Open Definition" selects constructor instead of class definition.
Workaround: Double-click on corresponding class node entry in the "Search" result view.

29215

"Open Definition" and "Definition" menu item are enabled when current editor selection is not valid.

29254

"Show/Hide Target Settings" in Project menu is only shown in Manifest Explorer, but not in project explorer.

Workaround: This command is only relevant to the Manifest Explorer view.

29262

Cannot Tab to OK and Cancel buttons in the new Curl project, new Curl package, new Curl file, and Curl prefrerences dialogs if focus is on the dialog page.

29268

Curl preference pages cannot be found using the preferences dialog filter.

29086

Opening a file from the search result view (double click) can result in the VLE to be launched, instead of the editor, when the file was last opened by the VLE.

Workaround: Use Open With menu and pick the Curl Editor.

29425

On Linux, sometimes when you open a Curl file the Curl editor commands are disabled.

Workaround:
You can refresh the commands to be enabled by toggling focus of the Workbench window. You can also click another editor or any Eclipse part, and click back in the Curl editor.

29439

If you Ctrl+N (shortcut for New) from the Manifest Explorer or the Definitions view, and then selecting Curl, and then selecting one of the Curl wizards (for example Curl File) will result in a blank view.

Workaround:
Perform the Ctrl+N from some other view, or use the File | New menu pick.

29503

The Curl manifest file is currently not synchronized with the file system. If you delete a component using the Manifest Explorer view, the file itself is not removed. Also, if you delete a file, for example by using the Project Explorer view, the component representing the file in the manifest file is not removed.

29545

If the same file is opened in the Eclipse Curl editor and in the VLE, and this file is saved from the VLE, when switching to the Eclipse window a popup dialog "File Changed" is displayed. This dialog mentions "The file has been changed on the file system. Do you want to replace the editor contents with these changes?". You should click on the "Yes" button.
This dialog is not needed because the Eclipse editor has already received the new contents from VLE before the dialog gets displayed.

29561

In the VLE, if you make a change to an applet or a fragment and take an action (in VLE) to navigate to the Curl editor, then any selected text in the Curl editor may not be accurate.

For example, if you add a control, and from the Event Handlers tab select an event handler, and click its {} icon, and if the VLE must create a new event handler (hence change the applet file buffer), then the text selection in the Curl editor to show the added event handler is not accurate and off my some number of characters.

Workaround: Save the file before navigating to the editor, or repeat the navigation. In the example above, click the {} icon a second time.