vb.net is SOOOOOOO annoying.
I am drawing a list of lines to a control. So, I declare:
In code, I have a custom Class called "Line".Code:Private Lines As New List(Of Line) Private CopyOfLines as New List(Of Line)
I am wanting to reuse the list called "Lines" so I can start a new list while retaining the old list. So I copy it's contents to "CopyOfLines", then clear the contents of "Lines":
Problem is the contents of CopyOfLines ALSO gets cleared! Is there no way to break the connection of "CopyOfLines" to "Lines"? This seems so unnecessary. After all, if I say:Code:CopyOfLines = Lines Lines.Clear
Then (b) will still = 10 while (a) = 0.Code:a=10 b=a a=0
Why does vb.NET have to break such simple logic and turn it into a gargantuan issue?I wouldn't mind it as much if the MSDN library would make it possible to find references to "List (Of whatever)", but all I get are references to text in a textbox. It seems that every time I go to the MSDN, I get a convoluted, runaround explanation or simply no documentation of something someone has done in their own code? Where did THEY find the information?
(Now I know why only 19% of vb6 users went to vb.NET.)![]()





I wouldn't mind it as much if the MSDN library would make it possible to find references to "List (Of whatever)", but all I get are references to text in a textbox. It seems that every time I go to the MSDN, I get a convoluted, runaround explanation or simply no documentation of something someone has done in their own code? Where did THEY find the information?
Reply With Quote