Multichoice PromptForChoice does not work as intended in ISE or VS Code. about plaster HOT 10 CLOSED

I'll have to look into this, maybe there's some way for PSES to know how to deal with this appropriately. Still won't be possible to allow multiple selection with VS Code's selection box, so I'm not sure what the right UI would be in this case...

from plaster.

Yo does it somehow:

From the Usage animated gif on the extension's marketplace page.

from plaster.

Heh, interesting hack. They're basically showing the same list multiple times with special characters to show the checked state. Pretty clever. I think we can replicate that.

from plaster.

I was wondering why PromptForChoice wasn't doing this itself. Odd the way it works.

from plaster.

Could you potentially do this for all prompts to get better formatting and to handle timeouts and errors more appropriately?

I think the way it formats by defaults is a little jarring at times for an end user. Descriptions and Names show up in different type fonts or in different places.

from plaster.

Could you give an example of what you mean? Unfortunately I don't have a lot of control over VS Code's UI

from plaster.

I guess it isn't that bad if you remove the multichoice options. The one quirk is the '-' that shows up for choice options.

from plaster.

Also, when running this from the debugger, we still have this issue where "blank" input is not passed back to PowerShell. This makes it impossible AFAICT to end a multichoice input from the debug console (without aborting the script).

from plaster.

from plaster.

@gerane This is not really a Plaster issue. Could you submit this issue to the https://github.com/powerShell/vscode-powershell project?

from plaster.