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 1 year and 10 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.
Product: PowerShell Studio 2022 (64 Bit)
Build: v5.8.205
OS: Windows 10 Pro (64 Bit)
Build: v10.0.19044.0
It was also seen on version prior to 205 version 201 (I believe). So what I have is my predecessor had a made a script with a splash screen that does a fade in, basically from here https://info.sapien.com/index.php/guis/ ... de-in-form
The script works great until I try to run it on a machine that does not have .NET 3.5 installed. What I see when it loads is nothing pops up, but in task manager I see it stuck (trying to load) on the splash screen, which I can only assume it is trying to initialize. Now, I wouldn't think not having .NET 3.5 installed would cause this but it is the only thing that has changed on the machine. I also don't see anything in the event viewer as far as errors or crashes.
Does your script run as expected when you run it in a PowerShell console from your machine? not currently
"It was also seen on version prior to 205 version 201"? Meaning I experienced the same results prior to updating to 5.8.205
I think I am narrowing it down. In previous versions of Studio we were able to set variables, like I show in the code above, in the timer_tick section. It appears now that it doesn't see those variables? Can we still do that or it is not possible anymore?
$timer1_Tick =
{
#TODO: Place custom script here
If ($Darker -eq 1)
{
The red is no longer working. It sees $Darker as $null, not 0 and not 1 So the timer1 tick runs constantly, never ends. Unless there is a setting I am not aware of.
From the script you provided above, you never set the variable outside of the scope of a script block. This isn't something we changed, this is how PowerShell scoping rules work.
From the scope of your $timer1_Tick script block, $Darker was never defined.
That fixed it. So I must say it did work on an older version of Studio because we have it running currently, but with studio referencing .NET 4.x it stopped. That's what I was tying to do, upgrade all our scripts to stop using .NET 3.5 and this was one that was compiled with 3.5. Hence it broke when I compiled it with 4.x
This topic is 1 year and 10 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.