/**
* setup a dummy mortgage payment that gives us a large set of values so that the table can resize
* its columns based on what is likely a "worst-case" scenario. this should leave plenty of room
* for real mortgage payments without making the window overly large and yet still reacting to
* local system visual sizes.
*/
private void sizeMortgageTable() {
resetMortgage();
final MortgagePayment p = new MortgagePayment(999999.99, 999999.99, 999999.99, 99999999.99);
paymentsModel.setPayments(new MortgagePayment[] {p});
paymentsTable.resizeTableColumns();
paymentsTable.limitTableViewport(VISIBLE_PAYMENT_TABLE_ROWS, true, false);
resetMortgage();
}
