Progressbar visible set to false when sub form is loaded

[dan.potter]

[dan.potter]

test.zip

(25.73 KiB) Downloaded 153 times

forum ate my last post??

[jvierra]

test.zip

forum ate my last post??

Fixed.

[jvierra]

It is never necessary to mess with scopt when calling between scrips and funcitons. Just pass the object.


in mainform

PowerShell Code

Double-click the code block to select all.

$button1_Click = {
	
	Call-sub_psf $progressbar1
	
}

In child form:

PowerShell Code

Double-click the code block to select all.

Param($pb)

$form1_Load={
    $pb.Visible=$false		
}

That is all and it was what I meant when I said use arguments.

[Hanzoy]

You guys have to be kidding, it is so simple.
Thank you dan.potter and jvierra
Works perfectly

[dan.potter]

It is never necessary to mess with scopt when calling between scrips and funcitons. Just pass the object.


in mainform

PowerShell Code

Double-click the code block to select all.

$button1_Click = {
	
	Call-sub_psf $progressbar1
	
}

In child form:

PowerShell Code

Double-click the code block to select all.

Param($pb)

$form1_Load={
    $pb.Visible=$false		
}

That is all and it was what I meant when I said use arguments.

What is the drawback of changing the scope?

[jvierra]

What is the drawback of changing the scope?

Harder to maintain. Less readable. Exposes variables to being clobbered.

Scoping should always be as narrow as possible. The whole point of passing arguments is to avoid exposure. In programming we pursue a policy of maximum "data hiding".

New programmers tend to make this mistake due to lack of experience and because it is an easy fix.

Think of the thing those new to Windows admin do which is to make everyone an admin. It takes some time too learn how to get the job done without creating issues.