Create new "me"

[M O J O]

Hi,

Instead of doing this....
Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Form1
f.Show()
End Sub
End Class

I would like to make it generic by doing something like...

Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Me
f.Show()
End Sub
End Class

.... but "Me" is not accepted, neither is "Dim f As New TypeOf(Me)".

I would like to put the CreateAndShow in a base form and then inherit from
it and still be able to use the CreateAndShow method.

Any suggestions? TANKS!!! :o)

M O J O

[Steve Long]

Well then, too bad you need to go that route to gain any sense of self
worth. It would be so much better had you never answered this person's post
than belittle them. Shame does not teach. I used to do the same self-serving
kind of belittling that you know do but I rose above it to be able to give
greater support to more people. Perhaps someday, you'll try the same
"GhostInAK" <gh*******@gmai l.comwrote in message
news:be******** *************** ***@news.micros oft.com...

Hello Steve,

I'll berate whoever I want. Must you be so freakin sensitive? Grow a
pair, ya pansy.

-Boo

>-Boo,
Must you berate everyone?
"GhostInAK" <gh*******@gmai l.comwrote in message
news:be******* *************** ****@news.micro soft.com...

>>Hello M O J O,

What's the point of this? If the goal is to not have to call .Show
when you create a form (lazy-ass).. then add Me.Show to the base
form's ctor. -Boo

Hi,

Instead of doing this....

Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Form1
f.Show()
End Sub
End Class
I would like to make it generic by doing something like...
Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Me
f.Show()
End Sub
End Class
... but "Me" is not accepted, neither is "Dim f As New TypeOf(Me)".
I would like to put the CreateAndShow in a base form and then
inherit from it and still be able to use the CreateAndShow method.

Any suggestions? TANKS!!! :o)

M O J O

[Steve Long]

Perhaps your right mg. Also, perhaps he's never heard the saying, "people
don't care what you know until they know you care."
"mg" <bi*****@gmail. comwrote in message
news:11******** **************@ k70g2000cwa.goo glegroups.com.. .

Watching Boo's replies to this and another recent post about retaining
changed values of a textbox, I think I see the reason. Boo does not
post to this NG to actually help anyone with VB, he's only here to show
everyone how much he knows. So if someone posts a question where he
can't do that, it shows in the caustic reply.

Boo, if the SNR is too high for you here, ignore it. As this is a
public NG, you are going to get all kinds of clueless nubes posting
stupid questions. Find a better way to deal with it so you can play
nicely.

GhostInAK wrote:

>Hello Steve,

I'll berate whoever I want. Must you be so freakin sensitive? Grow a
pair,
ya pansy.

-Boo

-Boo,
Must you berate everyone?

"GhostInAK" <gh*******@gmai l.comwrote in message
news:be******** *************** ***@news.micros oft.com...

Hello M O J O,

What's the point of this? If the goal is to not have to call .Show
when you create a form (lazy-ass).. then add Me.Show to the base
form's ctor. -Boo

>>Any suggestions? TANKS!!! :o)

M O J O

[Cor Ligthert [MVP]]

Mojo,

Public class myform
Inherits myBaseForm

https://msdn.microsoft.com/library/d...tminherits.asp

Cor

"M O J O" <MO**@discussio ns.microsoft.co mschreef in bericht
news:17******** *************** ***********@mic rosoft.com...

Hi Cor,

I was hoping that since my shared sub was inside a class, vb somehow new
what type of class the shared sub was called from.

I'm building a CRM system for my company. I want to have a base form that
can inherit all my form from. This base form will have many base stuff
....
forexample I will have three diferent ways to create and show a form ...

1) Normal - just create the form and show it.

2) Single instance - if the form is not yet created, create the form an
show
it.

3) Single instance by ID - if for example the customer-form with customer
ID=xxx is not showing, create the form and show it, else show it.

Hope you get my pont.

Here's my code so far (beware of wrappings)....
Public Class BaseForm

Private _singleInstance ID As Guid
Private Shared _singleInstance s As Dictionary(Of Guid, BaseForm)
Public Shared Sub CreateAndShowNo rmal(Optional ByVal owner As
IWin32Window = Nothing)
Dim f As Object =
Activator.Creat eInstance(Refle ction.MethodBas e.GetCurrentMet hod.DeclaringTy pe)
DirectCast(f, BaseForm).Show( owner)
End Sub
Public Shared Sub CreateAndShowSi ngleInstace(Opt ional ByVal owner As
IWin32Window = Nothing)
Call CreateAndShowSi ngleInstace(Gui d.Empty, owner)
End Sub
Public Shared Sub CreateAndShowSi ngleInstace(ByV al ID As Guid, Optional
ByVal owner As IWin32Window = Nothing)
If _singleInstance s Is Nothing Then
_singleInstance s = New Dictionary(Of Guid, BaseForm)
End If

Dim f As BaseForm

If Not _singleInstance s.ContainsKey(I D) Then
Dim fa As Object =
Activator.Creat eInstance(Refle ction.MethodBas e.GetCurrentMet hod.DeclaringTy pe)
f = DirectCast(fa, BaseForm)
f._singleInstan ceID = ID
_singleInstance s.Add(ID, f)
AddHandler f.FormClosed, AddressOf SingleInstanceC losed
Else
f = _singleInstance s(ID)
End If

f.Show()
f.Focus()
End Sub
Private Shared Sub SingleInstanceC losed(ByVal sender As Object, ByVal e
As FormClosedEvent Args)
_singleInstance s.Remove(Direct Cast(sender,
BaseForm)._sing leInstanceID)
End Sub

End Class
If there's a better way to do it, please let me know.

Thanks!

:o)

M O J O

"Cor Ligthert [MVP]" wrote:

>Mojo,

It is possible to create objects from classes. But never objects from
objects. (Although object is a class itself as well. To be more precise
the
highest class from which every thing derives).

The startup form is a kind of strange thing in VB.Net (but handy) it has
inbuild a Sub main, where in it creates an object from itself. For the
same
case you use a Module or Shared Class in which you can create your form
object. Than you can create as much objects from that class as you wish.

I hope this gives an idea.

Cor

"M O J O" <MO**@discussio ns.microsoft.co mschreef in bericht
news:88******* *************** ************@mi crosoft.com...

Hi,

Instead of doing this....
Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Form1
f.Show()
End Sub
End Class

I would like to make it generic by doing something like...

Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Me
f.Show()
End Sub
End Class

... but "Me" is not accepted, neither is "Dim f As New TypeOf(Me)".

I would like to put the CreateAndShow in a base form and then inherit
from
it and still be able to use the CreateAndShow method.

Any suggestions? TANKS!!! :o)

M O J O

[GhostInAK]

Hello M O J O,

Ewwww.. YUCK.
Just use the .Show method with the Me keyword in your base form's ctor (to
hell with the shared functions). All that reflection gunk is noisy and ugly.

Public Sub New()
Me.Show()
End Sub

....Or better yet, stop bein a lazy-ass and call .Show yourself when you create
the form.

-Boo

Hi Boo,

Please see my reply to Cor.

:o)

M O J O

"GhostInAK" wrote:

>Hello M O J O,

What's the point of this? If the goal is to not have to call .Show
when you create a form (lazy-ass).. then add Me.Show to the base
form's ctor.

-Boo

>>Hi,

Instead of doing this....

Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Form1
f.Show()
End Sub
End Class
I would like to make it generic by doing something like...
Public Class Form1
Public Shared Sub CreateAndShow()
Dim f As New Me
f.Show()
End Sub
End Class
... but "Me" is not accepted, neither is "Dim f As New TypeOf(Me)".
I would like to put the CreateAndShow in a base form and then
inherit from it and still be able to use the CreateAndShow method.

Any suggestions? TANKS!!! :o)

M O J O

[jessica dennison]

hey it is me so give me a shout!!

*** Sent via Developersdex http://www.developersdex.com ***