Frontcannon

Major update by EdHarvey. Next: major update by MadJik? Would be a dream come true.

Couldn't you just edit your topic title?

I've noticed that, too, it's a huge problem when you're working with Pixel art. Rotating a selection or using Rotate/Zoom makes every object anti-aliased but that's exactly what you want to avoid when working with Pixel art..

Axle's entry looks like he just used Pixelate and then ran a Gradient Blur.

Yeah! I'll look forward to see some multi-lingual PlugIns

Jerry. Maybe I should begin to use the quote-tag.. I didn't want to copy everything I (and you) said in the other thread.

If they were raised multi-lingual, maybe. Hint: They aren't. See my thread for further discussion.

Looks very cool! Composition is pretty good.

Having a PlugIn which knows what translation pdn is using would be excellent, I haven't even considered that. I imagined it this way: The PlugIn author releases a PlugIn. It then is either 1. directly translated by a translator who edits the source which is provided from the author (less work for the author) 2. indirectly translated, meaning the translator makes a table of what translates to what and the author edits his PlugIn (more work for the author) The process is completed by the author releasing the PlugIn in either language (SmudgeEnglish and SmudgeGerman, for example).

So you do have to have the ability to code if you want to, say, translate the UI of Smudge (implying you have the source code)?

This is a question that came up while working with .pdn a few minutes ago. I noticed that I had several menues twice, in German and English (for example: 'Distort' and 'Verzerren'). Though that problem is likely to be the author's fault (pyrochild's PlugIns are all in the right -German- sub-menues), I'd love to see some of the more complicated PlugIns (best case: every PlugIn) to be able to be used in different languages. I think that's possible, but I have no idea whatsoever if that idea would impose a whole lot more work on the PlugIn authors or if applying some simple modifications to the source code would already do the trick. So some thoughts on this from experienced translators (Zagna comes to my mind) or PlugIn authors would be appreciated. Edit: I mainly refer to the UI!

Hey, I'm not angry at Rick for removing this feature or in general, the statement that caused this trouble was a -bad- guess. As I recall implementing pressure sensitivity was somehow getting more and more problematic so Rick removed it to save himself from unneeded and unwanted hassle. Hidden Content: family-unfriendly? Plus, I was a little drunk that night. I've noticed that when you edit a layer name it is copied into the clipboard. Why??

You don't really seem to care, though.

Alright...

Pen pressure has been removed since v.3.5 due to reasons I forgot. Rick couldn't be bothered to further include it as it seems to be a boring and complex programming effort that gives everyone a headache (?). No way to get it back. It could come back with v.4.0 or later, so the only option you have is to wait.

Who is the dead one, Possum?

That's a wonderful motive you have chosen, Sarkut! That art just demanded to be pixelised..

hint hint

No, why should it be? It makes it easier to pixelise, though, but I think that's completely up to you.

This looks like one of this freudian dream pictures

Gritty and chaotic, nice colouring! Like this very much.

Got it, got it...

Do we really need to open a new discussion thread for every new competition theme?

Maximal minimalism.

If this guy has the same attitude of just leaving when he's in a bad mood, I'm happy he's gone.