<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/107714/">http://git.reviewboard.kde.org/r/107714/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On January 8th, 2013, 9:02 p.m., <b>Alvaro Soliverez</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I say the rationale is sound, the payee should not affect the button state.
But it would be good to know why the schedule name is not checked when updating the button states</pre>
</blockquote>
<p>On January 8th, 2013, 11:33 p.m., <b>Allan Anderson</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Sorry, I accidentally skirted round that by commenting only on what seemed to be incorrect. In fact, there is no problem with the schedule name. slotUpdateButtonState() is called whenever the text of schedule name is entered or edited. However, that was not apparent because the button had already been enabled, wrongly, by other non-mandatory widgets.
</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Am I OK to ship now, please? I just have to remove the instructions that I'd commented out.
I'm inclined to leave for later this area - "The same area of code in transactioneditor.cpp has several more of these possibly unneeded lines, although not affecting schedules. For instance, even with these two lines out and with no mandatory fields completed, if a payee is selected and the memo, tag field, next due date or status is edited, the OK button again is enabled wrongly.
I don't really see any valid reason for 'slotUpdateButtonState()' to be in this section. What do the wise men think?"
Yay or Nay?
</pre>
<br />
<p>- Allan</p>
<br />
<p>On December 14th, 2012, 10:46 a.m., Allan Anderson wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KMymoney.</div>
<div>By Allan Anderson.</div>
<p style="color: grey;"><i>Updated Dec. 14, 2012, 10:46 a.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">The problem as originally reported was that in Schedules view, the OK button became enabled even though no schedule name had been entered.
It was found that the button became enabled as soon as a payee was entered. It was also found that this happened when an amount was entered.
For "payee", line 753 of transactioneditor.cpp has -
"connect(payee,SIGNAL(textChanged(QString)),this,SLOT(slotUpdateButtonState()))", and slotUpdateButtonState() has -
"emit transactionDataSufficient(isComplete(reason)",
and 'This signal is sent out whenever enough data is present to enter the transaction into the ledger.'
Similarly, for "amount", at line 826, the same line appears.
As neither of these fields is a mandatory one, I believe they should not affect the OK button status. So, as shown in the patch, I have temporarily disabled these lines. I have done numerous tests of schedule creation and editing, and manual entry and editing of transactions without any problem.
The same area of code in transactioneditor.cpp has several more of these possibly unneeded lines, although not affecting schedules. For instance, even with these two lines out and with no mandatory fields completed, if a payee is selected and the memo, tag field, next due date or status is edited, the OK button again is enabled wrongly.
I don't really see any valid reason for 'slotUpdateButtonState()' to be in this section. What do the wise men think?
</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Numerous tests of schedule creation and editing, and manual entry and editing of transactions without any problem.</pre>
</td>
</tr>
</table>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Bugs: </b>
<a href="http://bugs.kde.org/show_bug.cgi?id=311481">311481</a>
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>kmymoney/dialogs/transactioneditor.cpp <span style="color: grey">(72295a2)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/107714/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>