AndrewDavid
-
Posts
1,592 -
Joined
-
Last visited
-
Days Won
28
Posts posted by AndrewDavid
-
-
Hello @InterGraphenic
You will not only find it here, but also an answer that may rectify your problem
I remember the issue well. Hope this helps.
-
42 minutes ago, null54 said:
should be much faster
It definitely is. After deleting the XML Folders were loaded immediately.
Before I deleted it was hanging on my Effects folder (700) plugins (including the PS Filters) I had no choice but to end task,
-
On 10/9/2023 at 7:42 AM, frio said:
I apparently guessed correctly that it was some kind of saved settings mismatch and deleting "C:\Users\nnnnn\Documents\paint.net User Files\PSFilterPdn.xml" resolved the issue, but this might be a little confusing if someone doesn't know to look for that file.
@null54 Hi there buddy
Instead of posting a bug - I found the answer in the thread. What happened was your new installation locks the first directory in PSFilterPdn dialogue screen to Paint.Net/Effects because of that .xml file. It cannot be deselected. Can you imagine how long is took to load all my plugins in effects and its subdirectories? On a lesser computer I am sure it would crash. I saw you suggested searching your folder and below. All my Photoshop filters are in C:\Docunents\PhotshopFilters.
So by deleting that XML file unlocked the ability to change the searching directories. Issue resolved
Thanks @frio
-
Keeping you updated to what has transpired since last we talked.
The steps I have followed (in case I want to do it again.)
1. Export a template from the original Solution
InteliSense detects errors - corrects them and exports a clean solution2. Open the exported cleaned template - which allows me to create a new solution (Andrew David's Plugins) based on your project
It came out as a linked GIT Solution (All the lock symbols) Now here is the interesting part. Intel identifies errors in the code (I foundthat odd seeing as VS created the solution)
3. Go through each CS script and errors are easily corrected by adding some use statements to maybe 7 CS files.
All errors were corrected by inteliSense (These were the errors the export process detected?)
I was able to correct them all except this one.
4. I excluded that script from the solution and "viola" a clean solution (no errors anywhere, clean code and it allows me to build a working plugin)
I also learned that if I update any of the analyzers, it breaks the plugin. (There are updates available)I can also understand why you didn't post any .png files.
The solution has been uploaded to my GIT account privately.
I've added you as a collaborator if you would like to see for yourself.You may not like the ¨cleaned code , but I think you use a few tricks to get around errors
The part I like is no errors. No tricks
This is one of the first plugin (other than codelab) that uses the new infrastructure. Its best for me to keep on top of things.2 years and I can finally say thank you for all the experience
-
I will keep the crash log hereFound my mistake
SpoilerFile: C:\Users\Andrew\Documents\paint.net App Files\Effects\AndrewDavid\PdnV5EffectSamples.dll
Effect Name: PaintDotNet.Effects.Samples.Gpu.ZonePlateShaderEffect
Full error message: PaintDotNet.WorkerThreadException: Worker thread threw an exception
---> System.TypeLoadException: Could not load type 'ComputeSharp.D2D1.Interop.D2D1PixelShaderEffect' from assembly 'ComputeSharp.D2D1, Version=2.1.0.0, Culture=neutral, PublicKeyToken=dc35fa229f6881d8'. -
1 hour ago, Rick Brewster said:
You don't need to do any project conversions or wizards.
@Rick Brewster While your project was open - I updated and installed a few tools that automatically applied suggestion/corrections to the code. I learned not to update accessories while an active file is open. I accepted their remarks and applied them. Most of it was just house cleaning by inteliSense. One of the apps I installed was NuGet and the extension .Net Upgrade assistant.
So I know about push and pull. Ok - A chance to learn about GIT. Obviously I can do no harm to your repository because I don't have a key.
I just wanted to see the process to understand it. Can you see I am learning things. Now I understand it. Even did some old dos commands well.
What I don't understand is after loading the new beta version last night - your project shows an error regarding the D2D1.Assembly - which I'll guess is a newer version then what your project points to.
Well new update for VS2022 just kicked in.(17.7.5)
Now, You mentioned Net 8. Still in its beta phase I see. I just installed Net 7 last night and that caused my PC to go through an update process when I shut it down. I must say my computer has never acted better. If I ever design a plugin that runs on NET 7 - I'll worry about Net 8 (which I understand won't be released until next year. I would expect eventually I will get a notice of an update to your repo and I can see about cancelling the pending update I created. (I haven't found it yet.) Now to look at the updated software.
Comment 2 - Your plugin now fails to load.Severity Code Description Project File Line Suppression State
Error NU1301 Failed to retrieve information about 'ComputeSharp.D2D1' from remote source 'https://packagesource/FindPackagesById()?id='ComputeSharp.D2D1'&semVerLevel=2.0.0'. PdnV5EffectSamples C:\Users\Andrew\Desktop\MyVS2022Plugins\PaintNet510\PaintExamples\PdnV5EffectSamples.csproj 1
-
VS2022 has a wizard that will create a new project from an existing one. Sooooooo
Yes I ran it against your Plugin and it created a new project for me to play with.
It also showed me references to Net 4.0 in the project that required me to select 4.0 from the assembly reference which wasn't there. I selected the next highest version - and it resolved that issue - but I noticed something else. Turns out I didn't have the NuGet app installed. I had the extension, so never really encountered a problem. Your project file makes a refence to it. Installing now to clear that issue.
Man I am learning a lot from your repo. Rather than a donation, come up to Vancouver so I can buy you dinner,
-
@Rick Brewster
I have the alpha version installed. I Have your repository in VS2022 showing me the locked icons, Why is it now full of errors?New menus in VS2022 and Device manager just kicked in on my machine. I had the wrong Project loaded. I expected your repo would be in my quick access list but no - I have to access it from within VS2022.
-
I just played with your plugin to learn how it works. It was working and allowed me to make about 4 images. Then it stopped rendering the text (TimeNewRoman)
Looks like 7 years have gone by without any comments. Does anyone use it? I have a tiny need to see this plugin working again, however, with all the changes made with Paint.Net, Windows, Markup language, I would not be surprised to see the source code generate many errors in Visual Studio or Codelab. Form based plugins I have learned doesn't work well for a novice like me. But I did get a few to work. Your thoughts?
Comment2 - After using it for these 40 minutes, it works fine. All I did was restart paint again. I already tried that but 2 worked.
Imagine a PDN 810X2632X3 layers so far. That's about 200 lines of a total 1140. A one time tiny task. The font - times new roman I bet was the culprit. I never changed it from the default. Here's that font issue again.
-
1
-
-
2 hours ago, ozgurrrrr said:
ERROR_UNABLE_TO_REMOVE_REPLACED)
Could the file you are trying to save open in another application or marked read only?
-
20 hours ago, Bandit12345 said:
it appears as though an recent update .NET Framework broke my Paint.NET.
Hello @Bandit12345 I would like to add a few comments.
Rest assured nothing from Microsoft can break your installation of Paint.Net
This is how I see it - You restored your system to a point before you received the update where everything worked.
Now you can continue to use the computer in this state, with updates turned off, but you won't see anymore new features
released to WIN10 (Microsoft To Do is 1 example) or Paint.Net (GPU Enhancements)
I have seen these updates to .net framework which have no effect on Paint.Net because Paint.Net is now running mostly
on Net 7.0. It now also takes advantage of rendering with the GPU. Something Paint.Net couldn't do before.
If you are intent on keeping your installation protected from Updates, now might be the time to start looking
at a Win11 based new computer. I am. My PC does not have the hardware required to update and WIN10 will
reach its end of life next year. I am hoping someone comes up with a workaround for this issue.
This may become common issue so I rambled a bit.
Hope this helps with your pain
-
Thank you @Zin
Although the corrections now allow compiling in codelab, The Pan Slider Control does not function when the plugin is run. The good news is the ops DLL still works.
I am running Codelab 6.9 and the thread link led me to believe this issue was resolved.
-
2 hours ago, Bandit12345 said:
Now when I attempt to launch Paint.NET (v5.0.3 or newer) Windows locks up completely for 180 seconds, like clockwork.
I have seen this occasionally. After the 180 seconds, does it appear or give you any errors? There can be many issues WRT loading time.
How much memory and free disk space do you have? Let us know if further help is required.
-
@BlastOfBN Hey there. Looks like a simple answer to me. You have the ability to turn off Microsoft Defender as your anti virus protection. Open Settings and look in security to see if it is turned on. AVG or Avast may have disabled it. The screen you are showing would indicate Defender is disabled. Hope this helps.
-
Looks like I am the only one playing with your examples. They are invaluable in getting me up to speed in plugin development. I took a closer look at VS 2022 and found one of the extensions was not up to date. I remember updating VS2022 but not the extensions. I bet you can guess which extension was not up to date.
Having working examples allows me to break everything and put it back together. Just my method. I use Visual Studio Code to look at things, but now with the introduction of AI, I have to be careful in the VSCode app. What is annoying is the intellisense from Microsoft. Something I doubt you use. It will report errors in VS Code and once corrected and brought in VS2022 it creates numerous errors.
I believe the intent of these sample effects is to show all the changes in the naming conventions. Looking at the conversation in the Codelab thread showed me it was a work in progress. I do forget I am in a private thread but all this information is too important to keep secret. I was hoping to stay away until all these betas were complete. With your release yesterday, that day has come. Now to just wait for Codelab to catch up.
I am confident that one of your cs scripts still reflect an old method that you depreciated. I corrected it but now I'm not sure which one it was. It was related to the Bokeh Blur.
My copy assembled fine and works perfectly alongside yours.
The other lesson learned is how 1 DLL file can contain so many effects. I'll have to try that with some of my own builds.
-
34 minutes ago, Rick Brewster said:
Visual Studio will automatically download it as part of the NuGet package restore process.
I saw the error while looking at the source code in VS 2022. Did I not give it enough time? I know what you mean - but it didn't happen.
Replace "will" with "should". And yes - I made sure everything was up to date.
-
Does this need to updated for the latest release? I am getting a error regarding the Package ComputeSharp.D2D1(2.0.3)Lesson learned.
Source code ZIP did not contain the files. Your download of the plugin did which I copied over to the source code to resolve my issue.
-
13 minutes ago, toe_head2001 said:
I don't really understand your question.
If I understand correctly - she is trying to get her app to open from within Paint.Net.
-
19 minutes ago, Troy said:
why does Affinity Photo open it without a problem?
It doesn't have to know what specific graphic file type the file is (Commercial Product)
Paint.Net does need to know the specifics before it will open it. (Free product)
No better way to explain it.
-
8 minutes ago, toe_head2001 said:
Then you can start Paint.NET with the Visual Studio debugger.
If the solution is built by codelab, is this a necessary step?
-
9 minutes ago, AnneYusual said:
it's probably sitting there.
Found it
-
2 hours ago, AndrewDavid said:
My next step is to build something in codelab to get you started.
Place the 3 Files in a directory and open the .cs file in Codelab. Make a Folder for your plugin. Select File/Build and you will see the option to generate a VS solution. Select the folder you just created. Notice the pngs have been automatically added. Next step is open VS as administrator and open the generated ScrollGeneratorEffect.sln file. Look at the reference assemblies and see the difference to your Scroll Generator.exe App
-
1
-
-
Hello @AnneYusual
Welcome to the forum
Over the course of 6 years, I believe I have followed your path on my own as well. I feel your frustration tenfold.
Not often does Windows\Paint.Net\Visual Studio work well together but they can if you gain a little more understanding of the NET framework.
Rest assured you are hearing this from a layman that has a working understanding of the process of creating a plugin in Codelab - exporting to VS - Building a working plugin.
The route I see you followed is just building it in VS and creating a standalone application that works fairly well, but with all the new updates, I think it has lost some of its functionality. I downloaded and installed your app, created a random pattern, hit SVG but nothing happened, hit copy which did paste it to the clipboard.
From Paint I was able to save as a svg and create a shape based on the generated image. So trying to save as svg in your app may not work for everyone.
I was able to view your source code in Visual Studio Code (A must have) and noticed you chose a form based interface. The most difficult in my opinion from what I have seen. There are only a few plugins around that still working, but their time is limited Im sure.
The best place to start (from a plugin creation view) is with codelab. @BoltBait has done an excellent job providing the basic guidance through a series of tutorials on his website https://www.boltbait.com/pdn/CodeLab/
I just saw @Rick Brewster has something to say.
Continued - I just looked at you app in VS 2022. You have built it directly on the Net framework. Think of Paint as a interface with the Net framework.
Most of the terminology in your app is directly accessing the net framework without using any language Paint.Net understands.
My next step is to build something in codelab to get you started.
-
Can you confirm TreeGen has been removed from your plugin pack and no longer works?
Headaches trying to re write a form based plugin?
Windows 10 Updates break Paint.NET
in Troubleshooting & Bug Reports
Posted
I wonder if this is what caused the issue?