Imported symbols missing mouse-over popup

[Pavel Petrushkov]

Hey Thomas,

I see you reused some of my kdev-go code, nice to know it was useful to
someone:)

Unfortuntely I cannot help you with this issue. For similar feature in Go
it was enough to create
NamespaceAliasDeclaration with globalImportIdentifier() and set its
ImportIdentifier to namespace
that you're importing, but I see you already did that.

One thing I can point out is that your import statement ("import
importstuff") is not highlighted,
but it should be, since you're opening a declaration on it, right? So maybe
you should check
if that code does not get executed or something.

Otherwise I suggest debugging ContextBrowser::showToolTip to see where your
declaration
gets lost.

Btw, I cannot compile your plugin, I attached the error I get when running
build.sh. If you can
figure it how to fix this, I can take a closer look at your code later.

Best regards,
Pavel.

On Mon, Nov 23, 2015 at 8:01 PM, Thomas Brix Larsen <brix at brix-verden.dk>
wrote:

> søndag den 22. november 2015 20.20.47 CET skrev Milian Wolff:
> > On Donnerstag, 19. November 2015 18:53:29 CET Thomas Brix Larsen wrote:
> > > Hi all,
> > >
> > > I'm working on a plugin for the D Programming Language.
> http://dlang.org
> > >
> > > I currently have a problem with symbols declared in other modules not
> having
> > > the mouse-over popup. Here is a screenshot:
> > > http://brix-verden.dk/misc/imported_symbols_are_red.png
> > >
> > > The symbols add and testConstant are imported from "importedstuff".
> Here is
> > > what duchainify has recorded:
> > > http://brix-verden.dk/misc/imported_symbols_are_red.txt
> > >
> > > Any hints would be appreciated.
> >
> > Hey Thomas,
> >
> > where is the source code for your plugin?
> >
> > Are you importing the parent context of the imports? Maybe that's what is
> > missing? Afaik that is required to keep the import alive. But it may
> also be
> > something completely different... :-/ Without the source and an example
> to
> > test it I'd have to hard time to come up with a clear answer.
> >
> > Also, did you write a unit test for this issue yet - is it reproducible
> there?
> > Would certainly make it simpler to find a solution to this problem.
> >
> > Bye
> >
> >
>
> Hello Milian,
>
> I have just pushed the code to github.
>
> https://github.com/ThomasBrixLarsen/kdev-dlang
>
> I believe that I have imported the parent context correctly as "Find uses"
> in KDevelop is working. But the mouse-over dialog/window is still missing.
>
> To be honest I'm not sure how to make a unit test for this case as the
> problem seems graphical.
>
> - Thomas
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20151124/e8f19125/attachment-0001.html>
-------------- next part --------------
[asus at lenovo parser]$ ./build.sh 
~/docs/kdev-gotest/kdev-dlang/parser/libdparse ~/docs/kdev-gotest/kdev-dlang/parser

Neither a package description file, nor source/app.d was found in
/home/asus/docs/kdev-gotest/kdev-dlang/parser/libdparse
Please run DUB from the root directory of an existing package, or run
"dub init --help" to get information on creating a new package.

Failed to find a package named ''.
~/docs/kdev-gotest/kdev-dlang/parser
src/dparse.d(6): Error: module lexer is in file 'dparse/lexer.d' which cannot be read
import path[0] = /usr/include/dlang/ldc/ldc
import path[1] = /usr/include/dlang/ldc
import path[2] = libdparse/src/
import path[3] = libdparse/experimental_allocator/src/




*** If I manually clone libdparse project into parser/libdparse, it gets found, but then I get a different error



[asus at lenovo parser]$ ./build.sh 
~/kde/kdev-dlang/parser/libdparse ~/kde/kdev-dlang/parser
Performing "debug" build using ldc for x86_64.
libdparse 0.3.0-alpha: target for configuration "library" is up to date.
~/kde/kdev-dlang/parser
src/dparse.d(1743): Error: no property 'startLine' for type 'const(BlockStatement)'
src/dparse.d(1759): Error: no property 'startColumn' for type 'const(BlockStatement)'
src/dparse.d(1775): Error: no property 'endLine' for type 'const(BlockStatement)'
src/dparse.d(1791): Error: no property 'endColumn' for type 'const(BlockStatement)'
src/dparse.d(2052): Error: no property 'startLine' for type 'const(Parameters)'
src/dparse.d(2068): Error: no property 'startColumn' for type 'const(Parameters)'
src/dparse.d(2084): Error: no property 'endLine' for type 'const(Parameters)'
src/dparse.d(2100): Error: no property 'endColumn' for type 'const(Parameters)'
src/dparse.d(2366): Error: no property 'startLine' for type 'const(Type)'
src/dparse.d(2382): Error: no property 'startColumn' for type 'const(Type)'
src/dparse.d(2398): Error: no property 'endLine' for type 'const(Type)'
src/dparse.d(2414): Error: no property 'endColumn' for type 'const(Type)'
src/dparse.d(3153): Error: no property 'startLine' for type 'const(StructBody)'
src/dparse.d(3169): Error: no property 'startColumn' for type 'const(StructBody)'
src/dparse.d(3185): Error: no property 'endLine' for type 'const(StructBody)'
src/dparse.d(3201): Error: no property 'endColumn' for type 'const(StructBody)'