On Wednesday, 1 February 2017 at 22:03:34 UTC, Rainer Schuetze wrote:
>
>
>...
>

Thanks

>>
>> 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.


I tried building Mago and it seems it requires an earlier VS than 2015 as some of the libs report being out of date(MSVC ver 1900 vs 1800 or something)

Does the concord debugger extension require mago to build or is it a standalone project? Basically I'd like to be able to investigate the issues with some symbols not showing and possible ways to improve the debugging experience. I feel like I'll have to install a separate older version of VS to get it to compile though.

On 02.02.2017 01:45, Profile Anaysis wrote:
> On Wednesday, 1 February 2017 at 22:03:34 UTC, Rainer Schuetze wrote:
>>
>>
>> ...
>>
>
> Thanks
>
>>>
>>> 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.
>
>
> I tried building Mago and it seems it requires an earlier VS than 2015
> as some of the libs report being out of date(MSVC ver 1900 vs 1800 or
> something)

The release is built with VS2013, but Appveyor builds with both VS2013 and VS2015 (see https://ci.appveyor.com/project/rainers/visuald/build/1.0.103/job/t0u55ue4vk0u4e39#L799). Some tests require a special library, but I never cared to adopt this (this is another project I "inherited" from its original author, mago originates from http://dsource.org/projects/mago_debugger and is mostly Aldo Nunez' work).

>
> Does the concord debugger extension require mago to build or is it a
> standalone project? Basically I'd like to be able to investigate the
> issues with some symbols not showing and possible ways to improve the
> debugging experience. I feel like I'll have to install a separate older
> version of VS to get it to compile though.
>

the debugger extension is project MagoNatCC in the Expression folder of the MagoDbg_2010 solution. It must be compiled with solution configuration "Debug/Release Static DE". It uses parts of mago necesssary for expression evaluation (including reading debug info from the PDB through the DIA API).

On 01.02.2017 23:03, Rainer Schuetze wrote:
>>
>> 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...

Page up/down should work in this prebuild: https://ci.appveyor.com/project/rainers/visuald/build/job/9mjrm70mra6or98f/artifacts

Home and end don't seem to be supported, they also don't work in C++.

On Thursday, 2 February 2017 at 07:21:27 UTC, Rainer Schuetze wrote:
>
>
> On 01.02.2017 23:03, Rainer Schuetze wrote:
>>>
>>> 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...
>
> Page up/down should work in this prebuild: https://ci.appveyor.com/project/rainers/visuald/build/job/9mjrm70mra6or98f/artifacts
>
> Home and end don't seem to be supported, they also don't work in C++.

cool, thanks! One more minor nitpick. When hovering mouse over a class or struct constructor, it does not show the parameters like a normal function. (seems that "this" does not get resolved properly as a function)

On 31.01.2017 07:27, Profile Anaysis wrote:
> On Monday, 30 January 2017 at 19:36:37 UTC, Rainer Schuetze wrote:
>>
>>
>> On 28.01.2017 04:08, Profile Anaysis wrote:
>>>>
>>>> Not sure what you mean by "ordered last". Least recently used?
>>>
>>> Well, if the names are alphabetically listed, which it looks as if it
>>> is, then by using the characters(like z, or _, or ___, or whatever) to
>>> prepend the names will put them at the end of the list. This will move
>>> the "junk"(whatever you decide that to be, such as ufcs's) to the end of
>>> the list.
>>
>> Visual D has full control over the order, so no workarounds needed for
>> that. I added an option to sort by type (default on).
>>
>> You can grab a preview build here:
>> https://ci.appveyor.com/project/rainers/visuald/build/1.0.101/job/kgw7q005oqw4m5nf/artifacts
>>
>
>
> Cool, that is much better! Makes it useful to me now!
>
> One more simple request! ;)

I've made a couple improvements:

- new option to disable exact start match (searches case insensitive sub string)
- free functions show different icon than member functions
- aliases show other icon than variables
- without any match, still keep the completion box open to update when deleting the last character
- new sorting mode "by declaration", effectively sorting by scope as discovered by the semantic engine.

The last item more or less does what you requested for classes, though it doesn't sort the variables or functions per scope. It also prefers function local variables over class members or globals.

A preview build is available here: https://ci.appveyor.com/project/rainers/visuald/build/job/fmr6vf36vny6gbum/artifacts

On 01.02.2017 23:12, Rainer Schuetze wrote:
>
>
> On 31.01.2017 11:45, Profile Anaysis wrote:
>> Also, it seems sometimes it seems to fail and not list anything from the
>> object I initialized it on, when I backspace and type . again it pops up
>> differently(basically not showing the objects members then next time
>> shows them, then).
>>
>>
>> e.g.,
>>
>> type object.
>>
>> then backspace over the . and repeat and see if you get different
>> listings(one with object's members and one without, should be obvious
>> cause the first element in the list will be different).
>>
>
> I can reproduce this (I usually use explicit expansion with Ctrl+Space,
> so didn't notice so far). It seems the context is lost and a list of all
> symbols is shown. I'll investigate...

This should be fixed in the build found here: https://ci.appveyor.com/project/rainers/visuald/build/job/fmr6vf36vny6gbum/artifacts

On 04.02.2017 07:32, Profile Anaysis wrote:
> On Thursday, 2 February 2017 at 07:21:27 UTC, Rainer Schuetze wrote:
>>
>>
>> On 01.02.2017 23:03, Rainer Schuetze wrote:
>>>>
>>>> 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...
>>
>> Page up/down should work in this prebuild:
>> https://ci.appveyor.com/project/rainers/visuald/build/job/9mjrm70mra6or98f/artifacts
>>
>>
>> Home and end don't seem to be supported, they also don't work in C++.
>
> cool, thanks! One more minor nitpick. When hovering mouse over a class
> or struct constructor, it does not show the parameters like a normal
> function. (seems that "this" does not get resolved properly as a function)
>

Unfortunately, constructors seem to cause some trouble in the semantic engine, there is no information for parameter tooltips, too (see https://issues.dlang.org/show_bug.cgi?id=11942). It works for "__ctor", though.