Problem with equal sign alignment in hashtables

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 4 years and 4 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
michelverbeek
Posts: 3
Last visit: Tue Feb 27, 2024 5:23 am
Been upvoted: 1 time

Problem with equal sign alignment in hashtables

Post by michelverbeek »

Product: PowerShell Studio 2019 (64 Bit)
Build: v5.6.170
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.17134.0

Hello,
Hashtable equal sign align does not always work. After some testing I discovered the following:
1. Alignment is ok when assigning strings:
Img1.png
Img1.png (14.07 KiB) Viewed 2096 times
2. But when I substitute a string (in the above table) with a variable or function and then format (CTRL+SHIFT+J) the alignment is scrambled:
Img2.png
Img2.png (14.45 KiB) Viewed 2096 times
3. After unchecking ‘Align hashtable equal signs’ and formatting, I get:
Img3.png
Img3.png (15.13 KiB) Viewed 2096 times
When testing it occasionally worked, but I cannot reproduce this behaviour, or did I miss something? This function, as it now is, is unreliable, and I have unchecked the option and align manually. :(

Kind regards
Michel
Michel Verbeek
Wageningen University
User avatar
mxtrinidad
Posts: 399
Last visit: Tue May 16, 2023 6:52 am

Re: Problem with equal sign alignment in hashtables

Post by mxtrinidad »

Thanks for reporting the issue. Our team will look into it.
This topic is 4 years and 4 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.