PropertyBased UI: All PropertyBased Controls

[midora]

Put together an PropertyBased effect dialog, showing all valid combinations of properties and control types.

Just to have an idea what's available and how it looks in enabled and disabled state.

 

Enabled     Disabled

                      

Dll and VS Solution: PdnPropertiesAndControlTypes.zip

 

Edited March 8, 2021 by midora

[NSD]

Very nice job! Thanks.

 

Shouldn't Pan control enabled / disabled have a gray border reflecting the size of the canvas?

There are also some issues with scaling the Color Wheel control in the UI interface.

 

Edited March 6, 2021 by NSD

[midora]

2 minutes ago, NSD said:

Shouldn't Pan control enabled / disabled have a gray border reflecting the size of the canvas?

 

The plugin uses always the default constructor if possible. In this case the property has no idea about the canvas or an image. Typically you are adding a bitmap to the property. Still a border around the square (which is used in the case) would be a good idea (IMHO).

[midora]

On 3/6/2021 at 9:03 PM, NSD said:

There are also some issues with scaling the Color Wheel control in the UI interface.

 

I checked this on my laptop (1920x1080.) using 125% (Recommended and 100%. There was no issue, even in the case that the scrollbar was visible. But for sure in your case the issue is visible.

[BoltBait]

I don't think too many people use the full sized color wheel.

 

Read this for how to utilize the other sizes:

 

https://forums.getpaint.net/topic/880-codelab-v60-for-advanced-users-released-june-25-2020/?do=findComment&comment=548600

 

 

[midora]

@BoltBait This plugin uses the default constructors (if possible). It's not about how to fine tune. Just to show all available PropertyBased controls. You can also use it to check some issues. Like the bad tabbing in the radiobuttons or the open dark theme issues. But these issues should be discussed in other topics. I know CodeLab offers more controls but my understanding is that these are just fine tuned and presetted standard controls.

[AndrewDavid]

Hi Martin

I've been a fan of your plugins for awhile and just realized the name change. For your info, I'm starting to learn how to use VS2019 to create plugins. Create is not really the right word, recover would be better. I have the beta version of Paint.net installed and working on modifying some old plugins to learn VS. Your PdnPropertiesAndControls provided me with a valuable learning experience that I used to rebuild your plugin. I hope you don't mind my posting to GitHub for reference purposes. https://github.com/AndrewDavid007/PdnPropertiesAndControlTypes. It's too bad not every plugin is in GitHub.

[toe_head2001]

@AndrewDavid,

You added this line 270 times in PdnPropertiesAndControlTypes.cs

#pragma warning disable CA1416 // Validate platform compatibility

 

You should not ignore the warning in 270 places. Instead you should fix the issue in 1 place.

 

Add this to your AssemblyInfo.cs file:

[assembly: SupportedOSPlatform("Windows")]

[AndrewDavid]

@toe_head2001 thanks for having a look. More lessons learned  Anything else I can chew?

 

[midora]

13 hours ago, AndrewDavid said:

I hope you don't mind my posting to GitHub for reference purposes. https://github.com/AndrewDavid007/PdnPropertiesAndControlTypes.

 

Hi Andrew, This plugin is a source for developers, so it's fine to move it to the next level.

 

13 hours ago, AndrewDavid said:

It's too bad not every plugin is in GitHub.

 

You can say this also for every application (like paint.net 😉). There are always pros and cons. At the end it's the decision of the developer.

Great that you are improving your skills. Go on.

 

 

 

[midora]

I created an update of the solution (VS 2019) which uses .NET 5 and requires paint.net 4.3.0.

 

PdnUiAllPropertyBasedControls 4.3.0.zip

 

You have to update the references to the paint.net assembly (the project references the portable version).

 

[NSD]

I think this solution does not work in Visual Studio 2017.  Is that correct?

[midora]

1 hour ago, NSD said:

I think this solution does not work in Visual Studio 2017.  Is that correct?

 

I guess you are right. I switched to 2019 beginning of the year because I couldn't install some newer sdks.

[AndrewDavid]

@midora

The only reason I am using VS2022 (Preview) is because VS2019 does not support Net 5.0.

I just finished going back to 4.2.16 to play with codelab. The work that was put into that plugin is gold. Not only does it create error free plugins, it exports to VB 2019 with no errors. The same plugin was opened in VS 2022 and 2 errors that should be easy to fix are not. Net 5.0 doesn't play nice. Maybe some work still needs to be done to make it backward compatible. My turn to look at your plugin.

[BoltBait]

10 minutes ago, AndrewDavid said:

VS2019 does not support Net 5.0.

Not true. 

[midora]

3 minutes ago, AndrewDavid said:

The only reason I am using VS2022 (Preview) is because VS2019 does not support Net 5.0.

 

But I did this project using VS 2019. So maybe you missed any update. Even Net 6.0 should work.

 

 

[AndrewDavid]

@midora

5 hours ago, midora said:

You have to update the references to the paint.net assembly (the project references the portable version)

VS 2022 would not let me. Errors galore.

VS 2019 allowed me to change references, but when I debugged, I got all kinds of errors. It did create the plugin though.

 

@BoltBait

I stand corrected. Is it causing you grief updating CodeLab?

[BoltBait]

5 minutes ago, AndrewDavid said:

@BoltBait

I stand corrected. Is it causing you grief updating CodeLab?

 

Not really. I did have to update my 2019 VS to the latest build. But, other than that, building CodeLab went smoothly.  It is ready to roll out when Paint.NET v4.3 is released.

[NSD]

That's good news. But what will happen to toe_head2001's Project Templates for Visual Studio.
Will it be updated as well?

[toe_head2001]

Just now, NSD said:

But what will happen to toe_head2001's Project Templates for Visual Studio.

 

Yes, I plan to publish an update this weekend.

[NSD]

14 minutes ago, toe_head2001 said:

 

Yes, I plan to publish an update this weekend.

 

Well, only good news today! Thank you brothers. After so much COVID-19, we need something like that.

[midora]

47 minutes ago, AndrewDavid said:

VS 2019 allowed me to change references, but when I debugged, I got all kinds of errors. It did create the plugin though.

I didn't debug it. It is simple and just worked.

[midora]

There was one issue. Maybe someone could provide a hint.

Adding the icon to the resource always created code with the icon type byte[]. Means I couldn't use it as StaticImage. At some point I gave up and edited the .resx file (it's a text file) and changed there byte[] to Bitmap. This worked. The created .cs file got this type and I was able to use it as StaticImage. This is only an issue in the .net 5 environmment.