PowerShell Studio 2016 - BUG - Control Sets

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 7 years and 7 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
othman
Posts: 145
Last visit: Tue Nov 02, 2021 1:40 am

PowerShell Studio 2016 - BUG - Control Sets

Post by othman »

Product, version and build: 5.2.127
32 or 64 bit version of product: 64
Operating system: Win 10
32 or 64 bit OS: 64
PowerShell Version: n/a

DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM

When trying to interest control sets, into a groupbox, PowerShell Studio 2016 Crashes and Not Responding.

Reproduce:
-New Form
--Control:
---Interest: GroupBox
--Control Sets:
---Interest either: TextBox - Validate IP. (into groupbox)

PSS2016_Not_Responding.png
PSS2016_Not_Responding.png (6.93 KiB) Viewed 2407 times
DevinL
Posts: 1098
Last visit: Tue Jun 06, 2017 9:15 am

Re: PowerShell Studio 2016 - BUG - Control Sets

Post by DevinL »

I've managed to reproduce this on my end and have filed an internal bug report.

Thank you for bringing this to our attention.
DevinL
SAPIEN Technologies, Inc.
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: PowerShell Studio 2016 - BUG - Control Sets

Post by davidc »

This issue will be resolved in the next service release.
David
SAPIEN Technologies, Inc.
This topic is 7 years and 7 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.