Bugzilla – Full Text Bug Listing
| Summary: | Add new _prompt variable for boolean values | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Dmitry Matveev <dmitriy.g.matveev> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | marco, sarika.sinha |
| Version: | 3.5 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
I second this, but in favor of activating/deactivating single lines of the program arguments.
For example
${check_prompt:"Enable some feature":true|false:-enable this argument}
On starting the launch configuration you get a list where you can select/de-select the arguments to enable/disable, where the default is defined in the 3rd argument of the variable.
Unfortunately, we don't have resources to work on this. |
Build Identifier: I20100608-0911 It would be nice to have new kind of *_prompt variable (like string_prompt and others) for boolean values. ${check_prompt:"Enable some feature":false} Reproducible: Always