Rick Brewster

Zoom7000, if you specify DESKTOPSHORTCUT=0 as a commandline parameter along with /createMsi, then that property will be patched into the PaintDotNet.x86.msi file and you won't need to specify it when executing the .msi itself.

I remember considering both possibilities when implementing this (constrain to original vs. current ratio), and there was a strong reason for going with the original ratio. I can't remember why at this point, but the code for that stuff (the Move* tools and especially their history actions) is easily the most complex in the whole application. So I must have had a good reason. I'll revisit it at some point though and see if it still makes sense to do it this way, or if there's some possible workaround.

That'd be great, but we don't have any tablets to work with in the first place.

FYI, our Sharpen effect does use unsharp mask. It just has a simplified UI and a "friendlier" name.

Jonas is correct. I downloaded the SDK for Photoshop at one point to investigate this, and implementing a Photoshop Plugin host is no trivial task.

To quote from http://www.webservertalk.com/archive53- ... 93670.html,

We do not have any code that accesses the Internet except that which pings our website for update checking. All it does it download a text file. To reiterate from a previous post, If you built Paint.NET yourself from our source code ZIP, and enabled code signing (set environment variables SIGNPDN=1 and PDNPFX=[path to PFX file]), you would see the exact same behavior. Most Windows components (Notepad, for instance) will not exhibit this activity because their signatures are stored in catalog files and are not retrieved as part of the normal loading process. However, you'll see above that the .NET Runtime Optimization Service is also being "flagged." This Internet access you're seeing is not necessarily malicious, there just seems to be something that is performing an extra verification of the digital signature. What other security-related software have you installed?

Well, in xml's defense, chew could've exercised some restraint as well

Hmm. Sounds like it might just be a WindowBlinds bug then. You might try pinging the author about that.

Is there a file called PaintDotNet.Resources.dll ?

Does it happen if you try other themes? Not the normal ones, but ones from WB

What happens if you have WB enabled, but also leave the Themes service turned on? And what's the name of the theme you're using, and is there a place I can download it? I'm trying to figure out the exact scenario that causes this so I can file a bug on the .NET guys. This is not a bug in Paint.NET, but will affect any .NET app that uses the same stuff in the framework that we do.

That's exactly what I was looking for. On a hunch, does Paint.NET work if you switch to the Windows Classic theme?

Like I said, our code is not doing this. There is some other software on your PC that is causing this.

feverfive, Could you post a screenshot? I have a idea...

That is how it's supposed to be. You press S to go to Rectangle Select, and a second time for Lasso, third time for Ellipse, then fourth time for Magic Wand.

People are adding on to the thread mentioned in (2) above, so I'll quote the pertinent post here for clarity:

True ... hmm, must've overlooked that one. Bug filed.

You may have uploaded the original image instead of the modified one, or maybe, like you said, it was not saved at all.

PdnLib, PaintDotNet.Data, PaintDotNet.Effects, and PaintDotNet.SystemLayer already provide much functionality for whomever cares to use it. PaintDotNet.Data, in particular, makes it possible to read .PDN images from any other application. However, the editing facilities of Paint.NET (the tools, the four "tool windows", etc), were never designed to be dropped-in to other applications. If you were to be able to plug those into your app, you would basically be plugging all of Paint.NET in to your app. Things can only be componetized and abstracted so far.

The main things I've seen that cause Paint.NET to start slowly are the following: 1) You only have 256 MB of RAM and are running multiple anti-virus / anti-spyware / anti-malware programs. Paint.NET runs okay with 256 MB RAM, but having all those other "watchdog" services running really knocks the wind out of systems with less than 512 MB. Please note that I am NOT recommending that you disable these, I am merely explaining their impact on performance. 2) Your hard drive has not been defragmented for awhile. I recommend running the defragmentation tool that comes with Windows: Start -> All Programs -> Accessories -> System Tools -> Disk Defragmenter 3) You have less than 256 MB of RAM. I recommend getting more when you can 4) You have a very very slow CPU (like 300 MHz). I recommend getting something faster when you can Dan is also right that on "cold" startup, it can be slow if no other .NET app has been run recently. On my system Paint.NET comes up almost instantly (0.6 seconds CPU time as reported by Process Explorer) most of the time, but if I've just started up my computer it might take 5 seconds or so during which the hard disk grinds away. Then again, pretty much everything is sluggish right after startup on most systems. I've spent a lot of time optimizing Paint.NET's startup performance and have had a lot of help from Josh Williams (whose job is .NET performance). There are still cases, like those listed above, where all the optimization in the world won't save you.

We used a CHM before but it was a real burden for us to maintain, and it also was no easy task to localize (translate) it for other languages. As a stop-gap I've uploaded the Paint.NET v2.6 help to our website: http://www.eecs.wsu.edu/paint.net/doc/2.6/Help/en/ Give it a day or two for the search engines to pick it up, then search it by typing your search terms in to a search engine and adding "site:http://www.eecs.wsu.edu/paint.net/doc/2.6/Help/en/" to the end of it. For example, to search for "clone stamp" you'd type: clone stamp site:http://www.eecs.wsu.edu/paint.net/doc/2.6/Help/en/

Looks like usertrust.com is some site dealing with digital signatures. Every EXE and DLL in Paint.NET is digitally signed with our code signing certificate. It is possible that you have configured some setting somewhere to do some kind of online double-checking/verification of signatures attached to EXE or DLL files. I don't know where or what this setting would be, but it's the only thing I can think of.

Paint.NET will only try to connect to http://www.eecs.wsu.edu/paint.net , for the purpose of checking for updates every 5 days (unless you tell it not to of course). The installer has no network access code in it at all. If any other activity happens, you have spyware/malware that is injecting threads into the PaintDotNet.exe process and doing other stuff.

My guess is it's just one of those other addons you have installed that's trying to jump in and start doing things, because I know for a fact that this forum does not use any ActiveX anything. Try Tools -> Manage Add Ons from within Internet Explorer and see if you find anything worth nuking.