Bug 312382 - edit fields are not editable anymore after certain actions
Summary: edit fields are not editable anymore after certain actions
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.8.0
Platform: MacPorts macOS
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
: 313468 330784 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-30 14:18 UTC by Marko Käning
Modified: 2023-04-13 03:45 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marko Käning 2012-12-30 14:18:24 UTC
Many edit fields of the application do take any inputs anymore after certain operations, especially after downloading transactions via HBCI.

What happens is e.g. that the "Search"-input line in the ledger would not accept any characters after the download.

Reproducible: Always

Steps to Reproduce:
1. Download transactions via HBCI
2. Try to input stg into the search edit field
Actual Results:  
Search edit field does not accept any character

Expected Results:  
Search edit field should accept any character

Even more annoying is that the transaction editor would not allow to enter anything in any fields after downloading new transactions, e.g. it is impossible to type in anything into the payee, category, tags, memo, number, amount edit-fields...

BUT, trying to edit the date seems to lift the restriction put upon the edit-fields, since suddenly they all can be modified again!!!
Comment 1 Marko Käning 2012-12-30 14:19:32 UTC
Oh, I forgot to mention that this behavior first appeared when Qt went from 4.7 to the 4.8 version!!!
Comment 2 Jim Ragsdale 2013-01-23 00:35:53 UTC
I also have this problem.  I am running kmymoney 4.6.3 from macports on OS X 10.6.8 with qt 4.8.4
Comment 3 dan 2013-04-20 12:12:48 UTC
Same problem here with the mac port kmymoney4

After Saving the working file, my edit fields do not work any more (ledger)

thanks,
Comment 4 Marko Käning 2013-04-20 12:20:54 UTC
Hi Dan, which edit fields are you talking about? The transaction editor ones or others, like the ledger search input field? 

BTW, for the transaction editor I have found a workaround: if the input fields are all disabled just enter the transaction date string with your cursor (by mouse). Afterwards all other input fields are editable again. (This doesn't affect the ledger search input field however!)

Please let me know whether you observe the same on your machine!

Which MacOSX are you running? I am on SL.
Comment 5 dan 2013-04-25 00:47:25 UTC
Hi, it does not work for me (your workaround) for the transaction input fields.

As soon as I do Save As, editing becomes impossible.

And I am using Mountain Lion (OS X 10.8.3)



________________________________
 From: Marko Käning <mk-lists@email.de>
To: sh_pop_ca@yahoo.ca 
Sent: Saturday, April 20, 2013 8:20 AM
Subject: [kmymoney4] [Bug 312382] edit fields are not editable anymore after certain actions
 

https://bugs.kde.org/show_bug.cgi?id=312382

--- Comment #4 from Marko Käning <mk-lists@email.de> ---
Hi Dan, which edit fields are you talking about? The transaction editor ones or
others, like the ledger search input field? 

BTW, for the transaction editor I have found a workaround: if the input fields
are all disabled just enter the transaction date string with your cursor (by
mouse). Afterwards all other input fields are editable again. (This doesn't
affect the ledger search input field however!)

Please let me know whether you observe the same on your machine!

Which MacOSX are you running? I am on SL.
Comment 6 Marko Käning 2013-04-25 19:55:24 UTC
OK, so it looks as if ML behaves differently.

Anyway, I suspect you can edit those fields after a restart of KMM...
Comment 7 Cristian Oneț 2013-08-30 09:00:30 UTC
*** Bug 313468 has been marked as a duplicate of this bug. ***
Comment 8 Cristian Oneț 2014-02-06 10:10:54 UTC
*** Bug 330784 has been marked as a duplicate of this bug. ***
Comment 9 Jack 2023-03-14 00:17:50 UTC
It's ten years later, and much has changed.  Is anyone still seeing this problem?
Comment 10 Bug Janitor Service 2023-03-29 03:45:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Bug Janitor Service 2023-04-13 03:45:45 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!