Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSScriptPad / Form Designer Issues #115

Open
TMA-2 opened this issue Jan 28, 2025 · 0 comments
Open

PSScriptPad / Form Designer Issues #115

TMA-2 opened this issue Jan 28, 2025 · 0 comments

Comments

@TMA-2
Copy link

TMA-2 commented Jan 28, 2025

Description

Like Packager, I'm collecting PSScriptPad and Form Designer issues here. Some are common to both, and some are specific to the former. Most common issues also affect Visual Studio except where indicated.

Please let me know if you'd rather they be separated.

Common

Bugs

  • When new event variable or function stubs are added to the main script, they'll be placed at the top, regardless of any Using or #Requires statements or Param() blocks, which will obviously cause issues. Statements such as these that must come first should be checked for, with the event variable or function being inserted underneath.
  • Type-doubling in designer files. I've broken this out into a separate issue: Form Designer Redundant Typing #117

PSScriptPad-specific

Bugs

  • MAJOR: Variables, Scratches, Console, Options, and About dialogs draw UNDER the WinForms canvas, and Toolbox and Properties controls. The related WPF canvas and Toolbox & Properties controls do not have this issue.
  • The caret likes to move around very strangely in the Console. One of the most aggravating issues is the RapidSense popup — pressing ESC meaning to close the auto-completion clears the prompt text as well. I've also found it's very easy for the caret to move above or behind the prompt, but I don't have terribly specific details for when or possible correlations.
  • MINOR: Add a Code View option for designer.ps1 files as there's no apparent way to switch to code view. Not major, since the file can be opened in VSCode at the same time and the updates seen each time it's saved.
  • Dark Mode: Colors in the XAML editor need to be adjusted as they're very hard to read.
  • Dark Mode: WinForms canvas is still light, as is the WinForms Toolbox and Properties. Perhaps this is too difficult/improbable, as I think it's even the same in VS 2022?
  • Dark Mode: Text on many controls appears white. Very hard to read due to the low contrast, and I'm not sure if it's only the preview or if the control text color is being inverted programatically somehow, with the ForeColor set to (or at least displaying) 255,255,255 instead of the default ControlText.
  • Dark Mode: When switching between themes, the XAML syntax highlighting disappears (appearing as a single color) until the text is re-drawn.

Suggestions

  • Add configuration for keyboard shortcuts, or at least a guide? Possibly related to issue [FEAT] PSScriptpad-Profile.ps1 (or settings.json / settings.ini) config file #90
  • Have the 'Options' and 'About' toolstrip buttons toggle their respective prompts instead of only opening. I.e., clicking About should open it - clicking a second time should then close it, and if Options is open beforehand, it should trigger it to close before opening About. Vise-versa for Options.
  • No undo / redo toolstrip buttons. No undo / redo in form designers (unless I'm completely daft and it actually does have it).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant