Visual D 0.50.0-beta1 released

[Amex]

On Tuesday, 4 June 2019 at 07:45:56 UTC, Rainer Schuetze wrote:
> Hi,
>
> new beta2 available: 
> https://github.com/dlang/visuald/releases/tag/v0.50.0-beta2
>
>
> Changes from beta1:
>
> * check and report invalid non-empty DMD/LDC installation 
> folders
> * VC project:
>   - DMD: fix wrong selections for bounds check options
>   - LDC: added -mixin option
>   - added enable -mixin option to autogenerate files according 
> to the
> compilation model
>   - new option for -extern-std=c++xx
> * visualdproj:
>   - Error List: classify warnings and deprecations according to 
> the
> respective options
>   - bugzilla 19930: fix building projects with "&|<>" in 
> directory names
> * mago: fix conditional breakpoints "not supported"
>
> Rainer
>
>
> On 31/05/2019 18:30, Rainer Schuetze wrote:
>> Hi,
>> 
>> for the adventurous: I have just released a preliminary 
>> version of Visual D with some new major changes:
>> 
>> - there is now another installer available that includes DMD 
>> and LDC, so no additional setup steps necessary to get you 
>> going
>> 
>> - now checks for updates for Visual D, DMD and LDC and assists 
>> with downloading and installing
>> 
>> - experimental: highlight references to the same symbol as the 
>> one at the caret (to be enabled in the editor options)
>> 
>> - mago debugger extension: better dynamic type handling of 
>> classes and interfaces, show exception message
>> 
>> Grab it here: 
>> https://github.com/dlang/visuald/releases/tag/v0.50.0-beta1
>> 
>> Cheers,
>> Rainer


I've noticed a weird behavior in Visual D projects. In the file 
tray(the drop down at the upper right of the source code window 
to find opened files) some of the D files have a different icon. 
One is a large red and white D while most others are a small red 
D.

The large D's use all lowercase paths while the small D's used 
mixed case(this is not 100% every time though). (for example, I 
might see the file C:\Project\main.d and c:\project\test.d each 
with a different icon)

I have had it where the same file was opened with the two 
different versions as if it was different file... changing one 
then changes the other(requiring a reload)... which can be 
dangerous since it can cause loss of changes. This has only 
happened a few times though and it happens when the debugger 
breaks in to a file and that is open(again, rare though).

I guess it has to do with a direct string compare rather than 
first converting everything to the same case. s1 == s2 vs 
s1.toLower == s2.toLower.

It's not a big problem though but you might add it to your list 
in case you come across it while fixing other stuff. One of the 
key's will be the different D icons.

It seems somewhere in Visual D.