VisualD modding

[Rainer Schuetze via Digitalmars-d-ide]

On 14.08.2017 16:51, Johnson Jones wrote:
> On Monday, 14 August 2017 at 06:50:21 UTC, Rainer Schuetze wrote:
>>
>> You can capture the state of the line before default execution with
>>
>> mNextTarget.Exec()
>>
>> Maybe your code could just be moved up there to begin with.
> 
> Moved up where?
> 
> I see 'int rc = mNextTarget.Exec(pguidCmdGroup, nCmdID, nCmdexecopt, 
> pvaIn, pvaOut);'
> 
> which is about all that is used with mNextTarget.Exec, but it is calling 
> it rather than overriding it in some way.

That's how the chaining works, this call executes the default 
implementation of the command.


> 
> Once I get some progress I'll submit some patches, right now I'm just 
> toying around with it trying to see how it's all set up. While I can do 
> some things I feel like I'm gonna have to revamp some of the editing(all 
> optional) because I get pretty frustrated in Visual D due to time 
> consuming processes of wrangling with spaces.

Apart from "smart indentation", there is little that Visual D does to 
spacing, it's default VS behavior. Even the "elastic tabs" plugin works 
(in VS2015), and I like its functionality of keeping code vertically 
aligned automatically, but I don't think it's a good idea to enhance 
tabs for this as the code will look broken everywhere else. Instead, it 
should just fill in tabs/spaces as usual.

> 
> e.g., when one hits return it always seems to take them to the start of 
> the line, then tabs move one at a time instead of jumping to the 
> previous tab indention. One one had many nesting and about 10+ tabs, 
> this is time consuming, and must be done for each line. Similar issues 
> occur with backspace, delete, etc.

Do you have "smart indentation" enabled?

> 
> I can fix the bulk of this and tweak them as I use visual D for my own 
> projects once I get a handle on how to do that in visual D's source.  
> It's a bit more wacky than doing it in C# since it seems to use COM to 
> do it all, which means there is little documentation for it.
> 
> What I've noticed is that one can run a separate window from visual 
> studio using visual D and I think this will open some cool things for 
> the future, such as a real time debug view window that can list such 
> things as instantaneous memory usage(a graph, sort of like diagnostic 
> properties, etc), performance, variable values, etc. Although, that's 
> just conceptual now, but I can imagine it being a useful utility feature.
> 
> Right now I've got a simple console running displaying the debug 
> information so I know what is going on, but eventually that could be 
> turned in to something useful for actually coding and debugging in D.
> 
>