Hello,
I'm currently in powershell studio 2022 with a project I made a while ago. The project consist of a form, a global file and some other files. Now, I want to add a new form window so I click on add new files, select powershell form.
But then, when I'm in the main form, I cannot found any way to show it. Normally I do Show-formname or call-formname but nothing is showed. If I try $formname, nothing is showed. Samething happen when I check in the newly created form. I can only see the current form. What am I missing?
Thank you
Unable to call another form
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.
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.
Re: Unable to call another form
To call an another form from the main form, you cannot call the form object directly. You need to call the reference function. Is the form you added build setting set to include?
For more detail on this, the following articles might be helpful:
https://www.sapien.com/blog/2022/08/03/ ... -projects/
https://www.sapien.com/blog/2022/03/15/ ... roduction/
For more detail on this, the following articles might be helpful:
https://www.sapien.com/blog/2022/08/03/ ... -projects/
https://www.sapien.com/blog/2022/03/15/ ... roduction/
Brittney
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.