Private
_busyPrivate
_buttonsPrivate
_disposedPrivate
_enabledPrivate
_handlesPrivate
_ignorePrivate
_onit has to be named _onDidChangeValueEmitter
, since Gitlens extension relies on it
https://github.com/eamodio/vscode-gitlens/blob/f22a9cd4199ac498c217643282a6a412e1fc01ae/src/commands/gitCommands.ts#L242-L243
Private
_onPrivate
_pendingPrivate
_placeholderPrivate
_stepPrivate
_titlePrivate
_totalPrivate
_updatePrivate
_valueProtected
disposableProtected
expectingPrivate
onPrivate
onPrivate
onReadonly
pluginReadonly
quickReadonly
quickProtected
visibleStatic
Private
_nextIf the UI should show a progress indicator. Defaults to false.
Change this to true, e.g., while loading more data or validating user input.
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.
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 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.
If the UI should stay open even when loosing UI focus. Defaults to false.
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 optional current step count.
An optional current step count.
An optional title.
An optional title.
An optional total step count.
An optional total step count.
Protected
convertURLPrivate
dispatchHides 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.
Protected
update
A light-weight user input UI that is initially not visible. After configuring it through its properties the extension can make it visible by calling QuickInput.show.
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.)
A user pressing Enter or some other gesture implying acceptance of the current state does not automatically hide this UI component. It is up to the extension to decide whether to accept the user's input and if the UI should indeed be hidden through a call to QuickInput.hide.
When the extension no longer needs this input UI, it should QuickInput.dispose it to allow for freeing up any resources associated with it.
See QuickPick and InputBox for concrete UIs.