https://bugs.kde.org/show_bug.cgi?id=311481
--- Comment #3 from Thomas Baumgart ---
Yes, too simplistic, because now you can create a 'transaction' with some
missing fields. It is a scheduled transaction but what happens if you enter it?
This line serves a purpose when entering transactions in th
https://bugs.kde.org/show_bug.cgi?id=311481
--- Comment #4 from allan ---
(In reply to comment #3)
> Yes, too simplistic, because now you can create a 'transaction' with some
> missing fields. It is a scheduled transaction but what happens if you enter
> it? This line serves a purpose when enteri
There is one problem we are aware, but it happens almost only in Unity, and
that's the application not resizing correctly.
We are not aware of any issues with the menu bar. Could you file a bug,
with more details and perhaps a screenshot?
Thanks!
Regards,
Alvaro
PS. Please, always cc the mailing
https://bugs.kde.org/show_bug.cgi?id=311481
--- Comment #5 from allan ---
(In reply to comment #3)
> . but what happens if you enter
> it? This line serves a purpose when entering transactions in the ledger, so
> you cannot simply remove it.
Picking up on this point, the schedule may be ente
https://bugs.kde.org/show_bug.cgi?id=311481
--- Comment #6 from allan ---
There is a very similar problem, too. With the original code, opening a new
schedule and entering just an amount also enables the OK button. Again,
'Amount' is not a mandatory field.
Removing the same code line for 'Amo
https://bugs.kde.org/show_bug.cgi?id=311481
--- Comment #7 from allan ---
OK, I see it now. The 'fix' does fix the initial problem, allowing schedule
and Transaction entry. However, If the schedule is edited, say adding or
changing the amount, that appears to be accepted, but is not.
So, that'
On 13/12/12 10:49, Alvaro Soliverez wrote:
There is one problem we are aware, but it happens almost only in Unity,
and that's the application not resizing correctly.
We are not aware of any issues with the menu bar. Could you file a bug,
with more details and perhaps a screenshot?
Thanks!
Regard
https://bugs.kde.org/show_bug.cgi?id=311481
--- Comment #8 from allan ---
(In reply to comment #7)
> OK, I see it now. The 'fix' does fix the initial problem, allowing schedule
> and Transaction entry. However, If the schedule is edited, say adding or
> changing the amount, that appears to be a
