Intellisense madness

[Rainer Schuetze via Digitalmars-d-ide]

On 31.01.2017 07:27, Profile Anaysis wrote:
> One more simple request! ;)
>
> Could you "subsort" them based on inheritance? What I noticed for some
> of my objects is that I'm seeing the base class members interspersed
> with the members I added, e.g.,
>
> class X {x}
>
> class Y : x {y}
>
> listing is
>
> x
> y
>
> because the inheritance is flattened. But I'd rather see
>
> y
> x
>
> because it shows the most relevant members(the ones I created) first,
> then the next relevant, and so on.
>
> Probably adding a simple "is(A : B)" to your sorting compassion function
> would work. (e.g., if A is derived from B then list A first)
>
> This isn't a big deal for small classes but for complex hierarchies one
> almost runs in to the same problem as before.
>
> This may not be useful for all cases. If you can just check on the
> object being references, it would probably be better.

I'll have to dig deeper into the semantic analysis engine, whether this 
information can easily be made available, as it's written by someone 
else (the author of Mono-D).

>
>
>
> I have noticed a few other things:
>
> 1. I am used to hitting page down when the intellisense pops up so I can
> quickly scroll through the list a page at a time without having to take
> my hands off the keyboard. When I use page down in VD it scrolls the
> cursor. Not sure if it is possible to temporarily override/hijack the
> page down/up keys while intellisense is open. Down and Up keys work in
> intellisense correctly but they are slow to move. Would be better to
> also add the page keys and possibly home and end.

Yeah, I miss page up/down sometimes, too. Will investigate...

> 2. functions and variables in the list from different modules are
> intermixed. This isn't a bad thing since they are alphabetically sorted,
> but there is so much stuff in my list that it becomes less effective
> when I have to search for stuff.
>
> I don't think sorting by module would be a good idea but maybe you could
> color code the names, if possible depending on what module they come
> from, or sort phobos entries to the bottom and color code them vs
> modules in the project.

Not sure if this will easy become confusing, too. I'll think about it...

>
> I might try to implement some features at some point. I think I would
> like to get mago working better first though because I feel D's
> debugging is very poor at this point(sort of bare minimum). I just need
> to get it to compile ;)
>

If you want to hack on mago: You don't need to compile Visual D for it, 
it is a different (C++) project: https://github.com/rainers/mago.

I suggest you should focus on the Concord debugger extension MagoNatCC. 
It's installation for debugging is very simple: just copy the resulting 
DLL into <VSInstallPath>\Common7\Packages\Debugger.