Hey,
I am wondering if this is possible or i guesst best practice.
I have my main tab control with 3 tabs with each tab having another tab control inside (frmMain.vb)
tabA has 11 inner tabs (so to speak)
tabB has 6 inner tabs
tabC has 4 inner tabs.
Each tab as a few controls with each pretty much requiring some type of coding, i was wondering instead of having around 50+ sub routines in frmMainm that I can create 21 class (.vb files - one for each inner tab), no gui, just a class and link the a few "handles *.click" routine to each of the seperate vb file.
It seems it would be cleaner coding. I tried using inherits on my new .vb file (ex: cmdExport.vb) with
In my frmMain, I have no routine there. When i test this, clicking of the cmdExport does nothing
Is there another way to practice cleaner code / even more object oriented using event driven methods?
Thanks
I am wondering if this is possible or i guesst best practice.
I have my main tab control with 3 tabs with each tab having another tab control inside (frmMain.vb)
tabA has 11 inner tabs (so to speak)
tabB has 6 inner tabs
tabC has 4 inner tabs.
Each tab as a few controls with each pretty much requiring some type of coding, i was wondering instead of having around 50+ sub routines in frmMainm that I can create 21 class (.vb files - one for each inner tab), no gui, just a class and link the a few "handles *.click" routine to each of the seperate vb file.
It seems it would be cleaner coding. I tried using inherits on my new .vb file (ex: cmdExport.vb) with
VB.NET:
Public Class toolsExport
Inherits myProject.frmMain
Protected Overloads Sub cmdExport_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdExport.Click
MessageBox.Show("testing 1 2 3")
End Sub
End Class
In my frmMain, I have no routine there. When i test this, clicking of the cmdExport does nothing
Is there another way to practice cleaner code / even more object oriented using event driven methods?
Thanks