If the UI should show a progress indicator. Defaults to false.
Change this to true, e.g., while loading more data or validating user input.
Buttons for actions in the UI.
If the UI should allow for user input. Defaults to true.
Change this to false, e.g., while validating user input or loading data for the next step in user input.
If the UI should stay open even when loosing UI focus. Defaults to false.
An event signaling when the user indicated acceptance of the input value.
An event signaling when the value has changed.
An event signaling when this input UI is hidden.
There are several reasons why this UI might have to be hidden and the extension will be notified through QuickInput.onDidHide. (Examples include: an explicit call to QuickInput.hide, the user pressing Esc, some other input UI opening, etc.)
An event signaling when a button was triggered.
If the input value should be hidden. Defaults to false.
Optional placeholder in the filter text.
An optional prompt text providing some ask or explanation to the user.
An optional current step count.
An optional title.
An optional total step count.
An optional validation message indicating a problem with the current input value.
Current input value.
Dispose of this input UI and any associated resources. If it is still visible, it is first hidden. After this call the input UI is no longer functional and no additional methods or properties on it should be accessed. Instead a new input UI should be created.
Hides this input UI. This will also fire an QuickInput.onDidHide event.
Makes the input UI visible in its current configuration. Any other input UI will first fire an QuickInput.onDidHide event.
A concrete QuickInput to let the user input a text value.
Note that in many cases the more convenient window.showInputBox is easier to use. window.createInputBox should be used when window.showInputBox does not offer the required flexibility.