Oluseyi

Aha! Makes sense.

You see, the thing is, it's either open source (take a look at item 4) or it's not. I'm not telling Rick how to run his project; if he wishes to adhere to the principle of open source, however, then there has to be a way for third parties to distribute patches to the source (and modified versions, so long as they remain under the terms of his original and give full credit - ie, maintain the original copyright notice, etc). It's a niggling, niggling philosophical point, given the benefit of Rick giving this product away for free, so please don't look at it as complaining! No, not unsolicited ones. There have been occasions where I have gone and requested code from certain plugin authors so that I could release it with Paint.NET. I understand the rationale, plus the ultimate determination of what goes into Paint.NET is up to you, so that's fine. I do think there's value in adding digital tablet support, though, and I'll explain why in a bit. At some point in the near future I might make that investment, then, especially if I have a patch/changeset to accompany it. So here's where I elaborate on the value of adding this functionality to XP. The first thing is that the work to do so would mean you'd need a generic interface which is specialized for different specific environments. This could help those who are trying to expand Paint.NET's audience far beyond your original imagination, all while validating the power and portability of the .NET Framework. If it requires minimal work on your part - basically, validating a contributed patch and massaging it for stylistic consistency - and you get free hardware out of it...?! Whoo! Anyway, as I said above, I'm cool. I've got it working and I've decided on an attack vector. I'll share my progress as it occurs. (Don't hold your breath - PyWeek 6 starts tomorrow!) I did. Several times. It wasn't in the dialog box. See the attached image file. (I know about internet text amping up hostility. No hard feelings. I've been guilty of it many, many times myself. )

Or do like the dialog says, and use /skiprepairattempt... Wasn't in the dialog. Perhaps you have a different version?

To clarify, I did not build release and packaging. Given my early build problems, I proceeded to begin with a debug build (finally succeeded), then a release build (succeeded immediately afterward), and then attempted to run the binary. I presume the installer would have set up all the necessary references and so forth, though I really don't want to formally install a work-in-progress build from source. But that's just me. The rest of my post remains valid. Either way, thanks for making available an excellent application. Question: do you accept user feature contributions? In what format? I was thinking of creating a patch file and sending it to you so you can test and integrate it as you see fit.

The compiled build of Paint.NET does not provide these resources, and if you already have an installed version of Paint.NET, and did not build and run an installer from source, PdnRepair can not fix your issue. Just copy the resources from your existing install.

Hi. I've been using Paint.NET for a long time now, probably since just before its 1.0 release. I've upgraded frequently, installed it on every Windows box I've owned/maintained, and recommended it often to others. I use Photoshop, I use GIMP, but for a lot of things I prefer quickly bringing up Paint.NET - especially for quick bitmap edits required in my job as a web developer. I think the refusal to add tablet support for Windows XP is silly, but I eventually decided it was probably something I should look into since it was burned into my memory long ago that Paint.NET was "open source." I finally grab the sources, install Visual Studio 2008 onto my desktop and fire it up to build. Juggling around some general .NET annoyances not covered in the readme.txt file (specifically, that mt.exe does not like filenames with spaces in them, but no biggie), I get all configurations to build and attempt to run the binary. Missing resources. I click repair repeatedly, but the resources keep coming up as missing. Finally I figure it out - this thread was no help, and the respondent's attitude was damn-near hostile - and copy the resources from my existing Paint.NET installation. (Oh, and btw, by default PdnRepair.exe was not copied into the output directory for pdn itself, so I had to copy that, too. Very sloppy.) After all of this, I felt moved to make this post, and specifically this point: stop it. There are too many frictions involved in obtaining, unpackaging and building the source. While this may "protect" Rick in his mind, and while it is entirely in his rights to do so as the creator/owner of pdn, it discourages people from contributing in ways that could benefit everyone. I'm going to spend a couple of days implementing an Ink interface for non-tablet XP, and whether you like it or not that's something that a lot of your users would appreciate. There are probably people who, despite early fumblings, would have found one way or another to add value to the community (and, by extension, to you and your product), but they've been deterred by the complexity of even attaining a working build and the sheer hostility on this forum. (I moderate GameDev.Net, and I'm a well-known a******. But I'm always kind to beginners. It's punks who think they know everything I wantonly crush underfoot.) The worst part is that all this it still doesn't protect you, really. Okay, it took some doing, but I now have a working debug build. I'm skilled enough to subvert, reverse or modify most of your means for identifying that my build is derivative of your work, if I wanted to. All you've succeeding in doing is annoy me enough to actually post on your forums and rant about you in my first post. Wow. That's a record. Please, impress me - and lots of other people - and make it trivial to download, unpack and build a complete working install of Paint.NET with no external dependencies. It's good for everyone. Don't worry about the backspaceware specialists. Anyone buying their stuff was clueless to the superior value provided by authentic Paint.NET anyway. Don't hurt your real customers going after people who were never going to "do business" with you, like the RIAA. Peace and blessings.