Bug 335832 - Automake Targets In Project Tree
Summary: Automake Targets In Project Tree
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: Automake (show other bugs)
Version: 4.6.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-05 11:27 UTC by Nick Lee
Modified: 2018-11-21 14:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Lee 2014-06-05 11:27:11 UTC
In the previous versions of KDevelop, there was a very helpful filter on the project tree, which you could rapidly copy and paste between sessions, which allowed all the automake targets (generally 50 or so) to be excluded from a project.  This has been removed, and now causes the following problems when using automake projects:

- the make targets proliferate every time you do a distclean and rebuild - eventually you end up with hundreds (each one repeated many times) and have to close and reopen KDevelop to reduce them back to one of each
- there is no way of filtering out the make targets in the new project filter - this means that there are 50 or more make targets in the tree that make it very hard to find the source files
- when creating a new session, it now takes ages to filter out the unwanted targets - before you could just copy and paste the filter from another session
- when doing distclean and rebuild, you have to re-exclude all the unwanted files in the project filter, as it forgets about files that get deleted by distclean

In conclusion, I suppose I'm saying is there a way of restoring the old project tree filter, as the new project filter doesn't provide the same functionality?  It has now become very difficult to work with automake projects as the tree is permanently cluttered with files that are of no interest.
Comment 1 Andrew Crouthamel 2018-11-11 04:34:42 UTC
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!
Comment 2 Andrew Crouthamel 2018-11-21 04:31:15 UTC
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!
Comment 3 Nick Lee 2018-11-21 08:59:40 UTC
Yes, it's still a problem, but with slightly different behaviour in the latest version of KDevelop.  It still populates the source tree with all the automake targets when you import a project.  However, once you've excluded them all manually, it doesn't seem to proliferate, so that's an improvement.  That said, it's still quite cumbersome to remove all the targets by hand for each project you import; indeed, I don't understand why KDevelop would show them in the source tree in the first place!
Comment 4 Sven Brauch 2018-11-21 09:18:48 UTC
There should be a button in the project view toolbar (above the view) which hides all targets. It has a tooltip "Show targets". Did you try that?
Comment 5 Nick Lee 2018-11-21 10:26:29 UTC
I'm embarrassed to say I didn't notice that button.  Yes, that does exactly what I want, thanks.

In my defence, since KDevelop has moved to the new trendy flat monochrome icons, they all look the same to me, so I didn't notice the square with a triangle in it appearing between a load of other icons that all look very similar.  But that's another problem (though if you can, please make it be known that it's made the UI extremely hard to use for some).

But thanks for helping me filter out the automake targets, that's saved a lot of bother!
Comment 6 Sven Brauch 2018-11-21 11:23:32 UTC
You can simply change the icon theme back to Oxygen in your desktop configuration tool (systemsettings if you run plasma).
Comment 7 Nick Lee 2018-11-21 12:14:22 UTC
It is on Oxygen, but I'm running KDevelop as an AppImage, so maybe that's why it's using the wrong icon set?

I'm on Kubuntu 16.04, and it seemed like the easiest way to get the latest KDevelop.
Comment 8 Sven Brauch 2018-11-21 12:59:55 UTC
Ok, in the AppImage you are unfortunately stuck with the icon theme we ship, which is Breeze, since that is KDE's current default design direction. Sorry.

I think we should not try to load the Qt platform integration plugin from your system (which would make it use your icon desktop theme), since I don't think it is necessarily binary compatible :/
Comment 9 Nick Lee 2018-11-21 14:58:38 UTC
Ok, never mind.  I'll try and somehow get a non-AppImage version of KDevelop 5  (it's currently on 4.something) on Kubuntu at some point.  But we digress from the original topic.  Feel free to close!