calling public sub in Form

[Strahimir Antoljak]

Why can't I call a public function or sub defined in the main form of my
application from within a module or a class, all being a part of the
same assembly?

When I define public function in a class, I can call it from the form,
but if I define public function in the form and try to call it from the
class it does not work. Any idea what am I doing wrong?

Thanks,

Strah
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Chris, Master of All Things Insignificant]

You can, but you need to have an instance of the class to call it on, unless
it's a shared method.

//SomeModule
Dim F as New Foo
F.SomeSub <--This works fine

//SomeBadModule
F.SomeSub <-- Only works if Shared

Class Foo
Public Sub SomeSub()

End Sub
End Class

Hope this clears it up.
Chris
"Strahimir Antoljak" <sa*******@lang an.com> wrote in message
news:em******** ******@TK2MSFTN GP10.phx.gbl...

Why can't I call a public function or sub defined in the main form of my
application from within a module or a class, all being a part of the
same assembly?

When I define public function in a class, I can call it from the form,
but if I define public function in the form and try to call it from the
class it does not work. Any idea what am I doing wrong?

Thanks,

Strah
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[strah]

Hi Chris,

Your input helped. I was creating new instance of the
Windows.System. Forms.Form instead of my form... it helped me to see my
error by looking at your code. Thanks,

Strah

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Herfried K. Wagner [MVP]]

"Strahimir Antoljak" <sa*******@lang an.com> schrieb:

Why can't I call a public function or sub defined in the main form of my
application from within a module or a class, all being a part of the
same assembly?

You can do that if you make a refernece to the main form's instance
available to the module.

Providing a reference to an application's main form
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=accessmainf orm&lang=en>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[strah]

Hi Herfried,

This is precisely what I was looking for. One instance of the form per
session, and it is instantiated only in the beginning.

Thousands thanks,

Strah
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Cor Ligthert]

Srahimir,

You can see the samples from Herfried and there is more, however remember
that is is bad OOP and you will probably get in problems when your project
grows.

Just my opinion.

Cor

[Cor Ligthert]

Chris,

In my opinion is your solution not using the parent class(form), however a
new form.

(Using this is very easy by the way)
dim frm as new form2
frm.owner = me

Cor

[strah]

Hi Cor,

since you already put some effort replying, I would appreciate if you
could elaborate why is that bad OOP practice, maybe an example or two.

Thanks for your input in any case. I remember you well helping me in
several occasions so I think of your input highly.

Strah

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Cor Ligthert]

Strah,

The answer is in my opinion very simple the goal is to make classes
independent from each other.

In this case is your form2 is completely dependend from the properties on
form1

To say it in other words a change in a "name" of form1 will give an error in
form2 (and all other forms where you do it like this).

Cor

[strah]

Thanks Cor!
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!