Closed sigmaaa closed 7 months ago
The recent update enhances user interaction with debug and launch configurations in the Eclipse environment, focusing on the Espressif IDF UI. It introduces dialogs for selecting configurations, improves messages for better user guidance, and refines execution handling. The shift from asynchronous to synchronous execution in launch target changes ensures more reliable updates, while new classes and properties enhance the user interface and experience.
File Path | Change Summary |
---|---|
.../idf/ui/LaunchBarListener.java |
Switched from asyncExec to syncExec for handling activeLaunchTargetChanged ; updated conditional logic in update method. |
.../idf/ui/dialogs/Messages.java , .../idf/ui/handlers/Messages.java , .../idf/ui/dialogs/messages.properties , .../idf/ui/handlers/messages.properties |
Added new string constants and messages for debug and launch configuration dialogs and handling. |
.../idf/ui/dialogs/SelectDebugConfigDialog.java , .../idf/ui/dialogs/SelectLaunchConfigDialog.java |
Introduced new dialogs for selecting debug and launch configurations. |
.../idf/ui/handlers/RunActionHandler.java |
New class for handling execution events, including launch mode and configuration selection. |
πβ¨
In the land of code and wire,
Changes come as needs aspire.
Dialogs bloom like springtime flowers,
Guiding devs through config towers.
Sync and async, hand in hand,
Making launch sequences grand.
ππ
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@sigmaaa hi !
Tested under:
OS - Windows 10 ESP-IDF: v5.1.2
π΄ Please, update text with Upper Case for those words and delete extra words.
π΄ found a bug related to Launch Config name validation.
Create project A -> create Debug config "A config" -> Edit Debug Config -> Rename to "A" -> there is the warning message only BUT it is still possible to create one.
If ignore it - in this particular PR it leads to the bug with empty list:
@sigmaaa hi !
Tested under:
OS - Windows 10 ESP-IDF: v5.1.2
- Select a debug configuration with Run mode and click "Run" -> Popup appears with suitable launch config -> click launch -> verify functionality π’
- Repeat test 1 for launch configuration with Debug mode π’
- Delete Debug config -> try to debug launch config -> message that suggesting create a debug config π’
- Remove project from debug configuration -> try to launch/debug -> Edit config question provided π’
- Repeated tests with Multiple Launch Configs / Debug Configs π’
π΄ Please, update text with Upper Case for those words and delete extra words.
π΄ found a bug related to Launch Config name validation.
Create project A -> create Debug config "A config" -> Edit Debug Config -> Rename to "A" -> there is the warning message only BUT it is still possible to create one.
If ignore it - in this particular PR it leads to the bug with empty list:
Hi @AndriiFilippov, fixed messages in the latest commit. The empty list bug happens due to editing the configuration name to an existing one, which should not be allowed. It's a bug from Eclipse CDT, I guess and it will be easier to fix on the CDT side
@sigmaaa hi !
OK, in this case everything LGTM π
Description
This is an alternative to https://github.com/espressif/idf-eclipse-plugin/pull/806, since the approach with filtering run/debug configurations causes bugs and additional maintenance debt
Fixes # (IEP-957)
Type of change
Please delete options that are not relevant.
How has this been tested?
Test 1:
Test Configuration:
Dependent components impacted by this PR:
Checklist
Summary by CodeRabbit
New Features
Enhancements
Documentation