Gnucash has a tree of accounts using an expandable tree type of thing where you click on subcategories to expand them. With Oxygen-gtk it's very touchy about whether it'll let you open a subcategory; other themese seem fine. Currently under Fedora20-pre-beta, but I've seen this under many distros: oxygen-gtk2-1.4.0-1.fc20.x86_64 kde-style-oxygen-4.11.3-1.fc20.x86_64 oxygen-gtk-1.2.0-5.fc20.noarch oxygen-icon-theme-4.11.3-1.fc20.noarch oxygen-gtk3-1.2.0-1.fc20.x86_64 gnucash-2.4.13-5.fc20.x86_64 Reproducible: Always Steps to Reproduce: 1. Create a set of accounts in gnucash 2. Try and expand or close a subcategory by clicking on the > or down arrow for the category Actual Results: The subcategory often doesn't open/close - very tempremental Expected Results: It's easy to open/close Looks like this is gtk2; from the maps of the gnucash.
Does it work better if launched with OXYGEN_DISABLE_INNER_SHADOWS_HACK=1 environment variable set?
Created attachment 83432 [details] highlight of the tree section I'm talking about in gnucash
Ruslan: Yes, I'd say that's a lot better.
I confirm this is gtk2 can't reproduce here with gnucash-2.4.11 and gtk-2.24.17 Can you post the version of gtk2.0 you have ? Any chance you can test with earlier version of gnucash ? (and without the "fix" from Ruslan) I'll try upgrade on my side.
My current versions are: gnucash-2.4.13-5.fc20.x86_64 gtk2-2.24.22-2.fc20.x86_64 oxygen-gtk2-1.4.0-1.fc20.x86_64 (on Fedora 20) and it still happens. I've had the problem for many years, so I doubt going to an earlier version of gnucash will help.
So maybe I do not understand the problem. what do you mean by "With Oxygen-gtk it's very touchy about whether it'll let you open a subcategory;" Could you be more precise ?
As per the image attached in comment 2; the 'Accounts' tab shows a tree hierarchy. The tree hierarchy has sections that can be opened or closed; e.g. the Outgoing category has subcategories on my account set for food, telecoms, clothes etc - but by default it doesn't show all those - I just see Outgoing, clicking on the > arrrow at the side of Outgoing should open the subcategories and turn the > into a v, similarly clicking on the v should close it again and turn it back into just showing the summary. With oxygen-gtk often clicking on the > or v doesn't open/close the category - it just highlights that line.
This seems to be misplaced rendering of the widget. We must have missed some offset when rendering it as composited.
@Dave, thanks for the details. Now: 1/ I really can't reproduce that 2/ I just realized your oxygen-gtk version is pretty old (oxygen-gtk-1.2.0-5.fc20.noarch) Could you update to latest ? (should be 1.4.0. You could even try master) Compiling from source is actually not very hard. keep me posted
Sure, I would if I could find the source; projects.kde.org seems to be 502ing
ok, got the source, but let me just fix something; I actually already do have the 1.40 version of oxygen-gtk: oxygen-gtk2-1.4.0-1.fc20.x86_64 oxygen-gtk-1.2.0-5.fc20.noarch oxygen-gtk3-1.2.0-1.fc20.x86_64 I hadn't previously spotted there were that many fedora packages. So, with the git af76fc6 it still happens for me (I copied the built lib in over the existing one and restarted gnucash). Note when I say tempremental I mean it sometimes works; but normally for me it doesn't.
On 11/28/2013 10:56 PM, Dave Gilbert wrote: > https://bugs.kde.org/show_bug.cgi?id=327324 > > --- Comment #10 from Dave Gilbert <gilbertd+kde@treblig.org> --- > Sure, I would if I could find the source; projects.kde.org seems to be 502ing > yep. Hopefully this will get fixed at some point. In the meanwhile, git clone git://anongit.kde.org/oxygen-gtk
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
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!