Button Logic - Part 2
Posted on 2011-10-20
This is similar to the open question, but I feel like this question is more clear.
just like the last question with the removeButton. When something is added to the ArrayList the table is updated and the removeButton is enabled or disabled. This works great.
I have a similar issue with the submit button on my base form. The button needs to know if there is something in the table like the removeButton, but it also has to check and see if a project is assigned.
so the button is not enabled unless there is a project assigned and the table has something in it.
Like the removeButton if the table is empty and the user adds something the submitButton needs to check and see if the project is assigned, if it is then enables the button.
How would you go about the logic on this one?