Bug 379108 - Checking metadata display for targets in assignments
Summary: Checking metadata display for targets in assignments
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (Clang-based) (show other bugs)
Version: 5.1.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-23 07:15 UTC by Markus Elfring
Modified: 2018-11-05 12:36 UTC (History)
0 users

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 Markus Elfring 2017-04-23 07:15:44 UTC
I am wondering about the next detail during my use of the source code editor in the application “KDevelop 5.1.0-26.1”. I can get additional information displayed in a corresponding window after the mouse pointer is positioned over an identifier in an expression for a conditional statement. It seems that I do not get such a metadata display if I would like to inspect the same identifier when it is used within the target of assignments.

Example:
{
	struct my_info* ref;
…
	ref = do_something(my_work);
	if (!ref)
		return -ENOMEM;
…
}


Does different syntax colouring indicate also any further software development challenges there?
Comment 1 Kevin Funk 2018-11-05 09:25:01 UTC
Please rephrase, I don't understand your problem.

What do you expect, what do you get instead. Which identifier, at which mouse position.
Comment 2 Markus Elfring 2018-11-05 11:28:59 UTC
(In reply to Kevin Funk from comment #1)

Would you like to check displays around an identifier like “ref” again for the desired code comprehension?

The application “KDevelop 5.2.4-46.1” is working as expected.
Comment 3 Kevin Funk 2018-11-05 11:42:02 UTC
Markus, your question again is written in confusing manner and not helping.

Please, next time, just answer my question (not with yet another question, ideally).
Comment 4 Markus Elfring 2018-11-05 12:27:19 UTC
(In reply to Kevin Funk from comment #3)

I proposed to take another look at a bit of source code which can be similar to my example.
This software was considerably improved in the meantime, wasn't it?
Comment 5 Kevin Funk 2018-11-05 12:36:12 UTC
Not the right answer. You have another try. </sarcasm>