-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unsupported (Keep this Open) #1
Comments
MDI Windows take some tricks to get to work. Wontfix |
ImageScalingSize must be manually set to 16,16 if left at defaults in fbs files. Wontfix To elaborate, the behavior is different between 5.1 and 7.x If no value is set, 7.x multiplies by CTScale twice, which corrupts the next save. This is fine if the CTScale is 1. 5.1 doesn't do this, but it fails to scale the glyphs at all. If you manually set the default image scaling size to 16,16 in the FBS or XML load file, then it works correctly, however, if you edit the project at CTScale one default values do not save back to the FBS project, so they will be cleared out, creating the trouble again. |
Function CheckedList is not a sort of the entire list, but rather a sort of module by module. The base module requires this. Wontfix |
Fixed IsMDIContainer trouble by adding IsMDIContainer as an option in the tag and interception of the xml upon output generation. Ends up it was #1 'willfix'. This software can now edit itself. Slight restructure of code due to being generated from PowerShell Designer itself. Designer.fbs and events.ps1 now editable from within the software Fixed issue #11 regarding $PSScriptRoot by having the core powershell-designer.psm1 handle that standup. Designer.fbs and dependencies copied to Documents\PowerShell Designer
A TabPage must be added by doubleclick to a TabControl and not drag and dropped. |
If there are no spaces in a project edit window, like pushing the spacebar, then a 1000 loop occurs for every character typed which will cause high processor usage. All projects start with a hidden space in the Region Images. The first word in a project is immune to hints and function autoselect. This word is usually #region |
- Misconception here. Has to do with ImageScalingSize not saving appropriately.
"PowerShell 7 may multiply DPI for ImageScalingSize twice for some items at control creation. This is due to built-in advanced DPI support. If you change this property in the PropertyGrid, this is corrected making this 'bug' more of a 'design choice', but it is a difference in the application between PowerShell 7 and PowerShell 5."
The text was updated successfully, but these errors were encountered: