Rick Brewster

There is free software called "CamStudio" that lets you do this. It may be what he used. It's what I've used in the past.

Yeah those are coming for 3.0, don't worry. Like I said, 2.70 is more of a "2.65 with some of the plugins we wrote that have been popular... oh and update the URL's to point to getpaint.net" (like where it looks for the update manifest, etc)

I just haven't tried building from a location that has spaces in it. When there are problems in this area it's usually from not quote-escaping pathnames, especially when expanding environment or build variables. For example, if part of my build script looks like this, some_command %BUILDPATH%\%BUILDCONFIG%\blah.exe If BUILDPATH or BUILDCONFIG expand out to have spaces in them, then 'some_command' will end up with what it believes are multiple command line parameters. It's not that we don't "support" paths with spaces in them, we just don't really use them ourselves and it doesn't cause us trouble. As for mt.exe not being in the readme.txt, that's just a simple oversight.

Please stay on topic ...

Moved to General Discussion

I know, trust me I know It's coming. Progress is just slow because I haven't had as much time to work on it. Maybe I'll post some screenshots or something.

One thing to note is that if you install this, you will lose the 'layer merge' feature once the next Paint.NET update comes out. (or rather, once you install the next Paint.NET update)

(Cross posted at my blog: http://blogs.msdn.com/rickbrew/archive/ ... 81716.aspx) First off, eecs.wsu.edu was down for the last 24 hours or so, so things like update checking and the like were not working. Yes, there is a new domain name for Paint.NET, but all the installed copies out there are still looking to eecs.wsu.edu for their update manifests. Hopefully that will change soon: since v3.0 is taking quite some time to finish, I've decided to put out an interim release which will aptly be called ... v2.70. It will basically be v2.64 with a few bug fixes, and also some of the popular plugins that we have developed will be included. This includes the Glow effect, and the Distortion plugins (4 effects) that are currently available on our forum. I couldn't justify releasing a "v2.65" that only had some URL changes in it (to point to getpaint.net instead of eecs.wsu.edu), so I decided to make these plugins more widely available. While this will not provide much benefit to those that already have these plugins, please remember that the vast majority of people do not have these installed and so the v2.70 distinction is justifable Paint.NET v3.0 will of course also have these plugins, but we will probably improve the UI. Please note that these plugins will only have English text. (Edit: Someone was kind enough so as to provide a German translation for the new UI text in v2.70, so this is no longer the case.) We no longer have a German translator, and are thus unable to provide updates in this area. For the short term this means we have to be picky about what text we add in the v2.xx releases. In the long term, this means that Paint.NET v3.0 will not ship with a German translation. It will still be possible for the community to provide a language pack, like they have for many other languages. I hope to have a Beta release of v2.70 out within a few days.

eecs.wsu.edu is currently down. That's why.

I don't think our build process has ever been compatible with paths that have spaces in them. I can't remember if the readme.txt mentions this or not.

We're planning to include this in v3.0.

We don't anti-alias edges when you rotate with the Move Selected Pixels tool ... so, I don't know.

There's already an entire thread for this. Locked

Moved to General Discussion Please post in the right forum.

Exactly like the message says. That feature requires Windows XP. There are other threads on this and a FAQ entry, please search for them for further information.

Yes, this is how Vista icons work. The 256x256 version is expected to be in a compressed format. Otherwise they'd add 256 KB to the .ICO ... and thus 256 KB to just about every Vista executable.

Moved to General Discussion

JolleyKun, the thread has not been replied to for over a month. Please do not resurrect dead threads like this. Locked

Born2killx, Don't be a jerk. This is your last warning.

RejZoR, I'm not sure when this type of functionality would be feasible to implement, I'll be honest. I do like the general idea though; I would probably do this by implementing a "save destination" plugin framework, where the default of course would simply be the file system. This would then make it easier to add new save destinations (flickr, web site FTP upload, whatever). I've filed a bug to keep track of this.

JolleyKun, use the Private Message facility instead of hijacking this thread.

Right, it's working as intended. We don't resize the Tools box to fit within the main window, it doesn't work like that. It is not a child MDI window, it is simply a top-level owned window. It may look a little weird, but in general when you resize any application or website to be small the layout is clumsy.

I wouldn't be surprised if the Relief effect would be useful here.

Born2killx, stop commenting on things like you're an administrator or someone in charge on the project. Along with your inane posting habits, I'm so close to banning you it's not funny. Now, to answer your question Lil_AzZa, we definitely won't implement or add something like this to the forums. If you want to sell things you will have to handle it yourself, as I do not want to have to manage and support what is essentially a business.

There is no plugin framework for this.