java How to take user input from a textfield of one form and use it in another? (java)

[Shammikit]

 

i have a form called screen1 which is the first form.it has a text field called username_TextField. i want to take the user input from this textfield and use it for a sql statement in my second form.the code below is the one i have written but it gives me a error saying: Non-static variable username_TextField cannot be referenced from a static context. what could be the problem.please help.

String username = screen1.username_TextField.getText();   

 

[ShadySocks]

my guess is that screen1 cannot be static?

[Shammikit]

29 minutes ago, ShadySocks said:

my guess is that screen1 cannot be static?

i have changed the jframe and all other elements to public static in screen 1. i forgot to mention,the code that i mentioned before is inside a jbutton which is private.is this a problem?

 

 

[Nuluvius]

You just need a reference to the other form and for there to be something publicly exposed: Form A has a public property and an instance of A is passed into Form B. Form B can then access Form A's publicly exposed property.

 

This kind of architecture is highly questionable however as you should instead be thinking in terms of Model View ViewModel (MVVM) or Model View Controller (MVC) with the use of various abstraction patterns to decouple your view from your business logic. In other words you don't want to be mixing view and business logic, it is bad design.

[Fetzie]

Look up "Getters and Setters". Should do what you need.

[Nuluvius]

In any event why are you double posting?

[g el]

On 18/12/2016 at 1:25 PM, Nuluvius said:

You just need a reference to the other form and for there to be something publicly exposed: Form A has a public property and an instance of A is passed into Form B. Form B can then access Form A's publicly exposed property.

 

This kind of architecture is highly questionable however as you should instead be thinking in terms of Model View ViewModel (MVVM) or Model View Controller (MVC) with the use of various abstraction patterns to decouple your view from your business logic. In other words you don't want to be mixing view and business logic, it is bad design.

+1 for using a pattern like MVC (or MVVM) for this.

The simplest way to think about it as a starting point is how is the user switching between form 1 and form2, is there a button he clicked? In that case you are most probably calling a method that does the switch, can you give an extra parameter for that method with the values you need? When you start passing the values you need from form to form, you could not think of a class that does that communication, which gets you closer to a controller in the MVC, the data you need to send between forms is the model part.