Thread overview
Visual D Needs refactoring capabilities and better error handling
Sep 05, 2015
Prudence
Sep 06, 2015
Rainer Schuetze
Sep 06, 2015
Prudence
September 05, 2015
1. A simple "refactor" on the RMB popup on a word in the text editor. This is pretty common among modern languages and should be easy to add.

2. I'm routinely having to flip from the errors tab to the output tab because the output is not being processed for errors. (errors tab is empty, yet it shows there are errors(by number))


September 06, 2015

On 05.09.2015 18:49, Prudence wrote:
> 1. A simple "refactor" on the RMB popup on a word in the text editor.
> This is pretty common among modern languages and should be easy to add.

Reliable refactoring is never easy, and D is a pretty complicated language. As a first step I've recently added a "Find references" command but that doesn't yet work too well.

>
> 2. I'm routinely having to flip from the errors tab to the output tab
> because the output is not being processed for errors. (errors tab is
> empty, yet it shows there are errors(by number))
>

There seem to be some "not implemented" messages in the "Test Cloud" output window that show up in the Error List if you choose "Entire Solution" as the filter. I'll have to investigate where these come from.

September 06, 2015
On Sunday, 6 September 2015 at 09:14:49 UTC, Rainer Schuetze wrote:
>
>
> On 05.09.2015 18:49, Prudence wrote:
>> 1. A simple "refactor" on the RMB popup on a word in the text editor.
>> This is pretty common among modern languages and should be easy to add.
>
> Reliable refactoring is never easy, and D is a pretty complicated language. As a first step I've recently added a "Find references" command but that doesn't yet work too well.
>
>>
>> 2. I'm routinely having to flip from the errors tab to the output tab
>> because the output is not being processed for errors. (errors tab is
>> empty, yet it shows there are errors(by number))
>>
>
> There seem to be some "not implemented" messages in the "Test Cloud" output window that show up in the Error List if you choose "Entire Solution" as the filter. I'll have to investigate where these come from.

Ok, I had current project set(there is only one project) and it would not show the errors(I'd have to swap to the output window every time). Setting it to Entire Solution did work. I did't get any superfluous messages.