Direct2D1 RenderTarget Ambiguous Methods

[epicabsol]

I am trying to use Direct2D from VB.NET, and the RenderTarget.FillRoundedRectangle method is giving me ambiguity problems. Visual Studio says that there are 2 FillRoundedRectangle methods with the same signature differing only in passing the roundedRect parameter by value or by reference. This conflict is a difference between C# and VB.NET, and I think might be related to #456. This is both a massive pain and raises quite a few questions:

• Why do both methods exist? When would the caller want the method to change the value of the roundedRect, necessitating byref?
• I went looking at the source on GitHub to understand what each overload is doing, but not only is each function just calling another overload of the same function, the byref version of FillRoundedRectangle (and the other drawing functions) doesn't exist in the RenderTarget file. Well, I can see that the RenderTarget class is declared as partial, but GitHub search doesn't find any other definition of a "RenderTarget" class. How then can each function definition in RenderTarget.cs just call another overload of the same function? How is that not a stack overflow?
• Where is the actual code that defines the byref version of the method?
• Where does the RenderTarget drawing code - not just the FillRoundedRectangle, but all of it - actually go? Does SharpDX call into native Direct2D, or are the RoundedRectangle functions just helpers implemented in C#? If they are just helpers, I would be happy to copy the implementation myself.

Screenshot of peeking the definition of RenderTarget:

Please don't just write this off with a "SharpDX is just a C# thing" like #456.

[xoofx]

1. It is not to change the value but for performance reason when you don't want to bloat the stack with unnecessary copies (unfortunately, we don't have an equivalent for a const keyword)
2. You don't see the code because most of SharpDX code is auto-generated from DirectX C++ headers when compiling the project
3. see 2)
4. These methods are direct calls to Direct2D COM objects

And yes, SharpDX has been designed mainly with C# in mind, and I realized too late these VB language issues.

[Tiba3195]

I have this problem all over the place because I too use VB.net, so far I have just gone in each time and made a change to sharpDX.

I don't use any of the direct2D stuff but most of the boundingXXXX.intersect and contain have this problem as well as a few other bit here and there.

Best bet would be to fork it and make the changes u need, so far this has worked for me.... I use a custom toolkit(3.0.2) build for all my 2D stuff.