[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 194532] wish: improve kdevelop4 class browser usability
From:       <uetsah () googlemail ! com>
Date:       2009-05-29 15:31:34
Message-ID: 20090529153134.D1C8C165F8 () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #4 from  <uetsah googlemail com>  2009-05-29 17:31:28 ---
Thank you Andreas for pointing this out, with that option set it works for me
also.

Wouldn't it be a good idea to also tell the user about this in the class
browser itself, rather than to wait for them to complain on the bugtracker (or
elsewhere) like I did?
For example, when applicable, a floating text could appear at the bottom of the
treeview reading "n source/header files in currently opened projects not yet
parsed. *Info...*", where "*Info...*" would be a link which, when
clicked/hovered would show an interactive tooltip reading "Click here to *parse
all now*. Also, you may *configure* Kdevelop to automatically parse all files
when loading a project." (Where the links would, when clicked, bring about the
expected action / take you to the relevant configuration page.)

Also, for me it takes quite a few seconds until the entries start showing up in
the class browser, so what do you think of my feedback animation idea mentioned
in the original bug description?

By the way, thanks to David for those two small but useful fixes.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]