Fantastic video. So useful. It's funny how in coding, there is the written tradition and the oral tradition just like in a religion: if you read a book or take a CS course, you get only the written tradition, i.e., "To write an array, the syntax is for(i =...", which is like a catechism or liturgy that gets repeated ad naseum. Everybody knows it. It's nearly the same (like the Apostle's Creed) for every denomination/language, and yet this is what books and courses spend 95% of the time teaching. Then, there's the oral tradition. The really, really useful and essential information (like in this video). Ironically, experts all (mistakenly) think beginners can't code because they don't know the syntax and that this "oral" tradition (how to use Visual Studio, how to use a connection string to a database, etc.) is not really worthy of formal study and so it's passed on in the most obscure formats (you might be lucky enough to pick it up after years and years from a senior developer at work or weeding through all the terribly arcane--again, just like a religion where experts love showing off their arcane and abstruse knowledge that no one else can understand--posts on Stack Overflow). When, in reality, there should be more books and courses on things like this video covers. Rant now over. Thanks gain.
Use setter() and getters(). Alternatively, any public variable is directly accessible. As an example, if Form1 has a Public String name, you can access this variable in Form2 as String f1Name = Form1.name;
Great video, only issue is if you try to close form2 by hitting the "x" at the top right, wont form1 still be running in the background because it's set to hidden?
Use Application.Exit(); to make sure application is killed, or use Form.Close(); to close the form. Hidden might not be a good idea if you don’t plan to re-show the Form.
Good stuff hocam :)
ruclips.net/video/-IppJcCABnA/видео.html
Fantastic video. So useful. It's funny how in coding, there is the written tradition and the oral tradition just like in a religion: if you read a book or take a CS course, you get only the written tradition, i.e., "To write an array, the syntax is for(i =...", which is like a catechism or liturgy that gets repeated ad naseum. Everybody knows it. It's nearly the same (like the Apostle's Creed) for every denomination/language, and yet this is what books and courses spend 95% of the time teaching. Then, there's the oral tradition. The really, really useful and essential information (like in this video). Ironically, experts all (mistakenly) think beginners can't code because they don't know the syntax and that this "oral" tradition (how to use Visual Studio, how to use a connection string to a database, etc.) is not really worthy of formal study and so it's passed on in the most obscure formats (you might be lucky enough to pick it up after years and years from a senior developer at work or weeding through all the terribly arcane--again, just like a religion where experts love showing off their arcane and abstruse knowledge that no one else can understand--posts on Stack Overflow). When, in reality, there should be more books and courses on things like this video covers. Rant now over. Thanks gain.
For those who have problems with spawning the Form2:
after Form f2 = new Form2();
put f2.Show();
Very cool video. It helped me how to show / hide forms which I want
nice job man keep up the good work abi cok guzel
ruclips.net/video/-IppJcCABnA/видео.html
I liked your video, very understandable. Do you have any video on how to properly pass values as parameters between forms?
Use setter() and getters(). Alternatively, any public variable is directly accessible. As an example, if Form1 has a Public String name, you can access this variable in Form2 as String f1Name = Form1.name;
Great video, only issue is if you try to close form2 by hitting the "x" at the top right, wont form1 still be running in the background because it's set to hidden?
Use Application.Exit(); to make sure application is killed, or use Form.Close(); to close the form. Hidden might not be a good idea if you don’t plan to re-show the Form.
i cannot see "window form" in my adding window
What about when im working with OOP?
can we do this without linklabel (using simple lable or anything else) because it not looks too good
but your method is working thanks !
ruclips.net/video/-IppJcCABnA/видео.html