gege
-
Posts
34 -
Joined
-
Last visited
Posts posted by gege
-
-
An image worth a hundred words...
Hummm... I thought it was a thousand...
-
I've found another weird behavior: the new "help" menu does not react like a regular menu.
Steps to reproduce:
- click the "?" menu
- move your mouse to the left
- the dropdown menu disappears (which it should not)
- then, without clicking anywhere, move the mouse back to the right so that it hovers the "?"
- the dropdown menu appears again...
To summarize, it appears one has to be very careful not exiting the "?" area once he has clicked and go right to the dropdown otherwise it disappears. By comparison, the Effects menu - which is a regular menu - behaves normally: when going too far to the right after the click, the dropdown remains opened and you can go back to it and click a menu entry.
Hope this helps.
I noticed this too and it is really annoying. I even made a screenshot to illustrate it. The case is, after clicking the Help button, I tend to move mouse pointer diagonally in the bottom left direction (shown in red), which makes menu disappear.
Only when carefully moving mouse as shown in green I can effectively reach a menu item.
-
1
-
-
I think this is my favorite bug so far
It's kind of hilarious.I don't think it's a bug. It's "undocumented behavior"!
Well, now it's documented, so... whatever.
-
Muahah... I already decompiled the .resources and started updating my .resx... I'm unstoppable!
Well, I did it too. No more funny/nonsense phrases now
In fact, PT-BR it's almost completed. I'm just checking consistency of related strings (like Statusbar tips) and fine tuning the entire set of strings.
-
Have you calibrated your ClearType settings? (Control Panel > All Control Panel Items > Display > Adjust ClearType text)
Yes, I have. And, just to make it clear, both screenshots were taken on the same system, AFTER calibration. So, I assume it's not related to calibration.
Again, I don't take this as a big issue. We will end up getting used to it, I think. It's just that, when compared side by side, the old rendering looks better (for me, at least).
-
For now, if this causes you trouble, you can go into settings and un-check "Animations" in the User Interface section.
Well, it's not like it's causing big trouble. As I said, it's more like a small tweak to improve usability. And I think the other animations (such as when moving layers or reordering image thumbnails) are pretty neat. So, I'll stay with the nervous ants for now
-
I keep my taskbar on auto-hide and, when PDN 4 is maximized my taskbar will not show.
Oh, and I am not really liking the change of font for the titles. I'm not sure if there's a way to change this in-app but I prefer the pre-4 font(s).
I can reproduce the taskbar bug.
And, regarding font rendering, I'm trying to get used to it, but I still prefer it the 3.5 way too. Just out of curiosity, I took a screenshot of Edit menu in both versions and put them side-by-side. Sharpness in previous version is much better, IMO.
-
First things first: big thanks for this! I've been anxiously waiting to play with it for years...
This thing is pretty stable for an alpha release. After a couple hours playing with it, including use of lots of plugins, it hasn't crashed a single time. Where's the fun?
Now, seriously. As I said, no bugs found so far, but I'd like to point some usability issues that have bothered me:- Rotation handles are too intrusive: they are inside and outside the selection rectangle. I ended up rotating selections, when in fact I just wanted to move them. Maybe those handles should appear only outside the selection corners. This way the Move handle would be unnecessary, as any space inside the selection rectangle, plus outside space not around the corners would be a possible anchor for this.- Dancing ants are too nervous. I mean, they move way too fast. This is specially proeminent on small and irregular selections, like those made with Magic Wand. I just compared them with that other big well known image editor and its ants are much more slower than ours :-)- 'Tools' section of Settings dialog is visually confusing. Probably due to flatness of that page design, it is really difficult to figure out each setting on first sight.- Settings dialog takes too long to open, showing '(Not reponding)' on titlebar. Fake edit: in fact, this occurred the first two or three times I opened it. Now, it opens relatively fast.- Automatic translation is often funny (and yes, I have read your blog comment on this). You will seriously need some human help here and I can land a hand on this for Brazilian Portuguese, as I have a lot of experience* with volunteer translation.*For example, I have made contributions to OpenOffice in the past and also, for several years now, I'm the sole translator of MediaMonkey player into pt-br.-
1
-
-
Brazilian magazine INFO EXAME (biggest technology magazine in Brazil), released today a nice Paint.NET review.
It is in Portuguese, so I tried to translated it to English. I hope there's no big grammar mistakes :oops: , but if someone finds some errors in the text below, please drop me a line. Here is the full article:
Paint.NET gives Microsoft Paint an upgrade
This program started as a students project at Washington State University using Microsoft's .NET Framework and its graphic libraries. The idea was to create an alternative to MS Paint, which is bundled with Windows. After the project's conclusion, developers -- then already graduated -- continued releasing new versions of Paint.NET.
As an image editor, it won't replace Photoshop, of course. But it allows some advanced image editing at no cost. Paint.NET has support for layers, for example, a feature that makes the difference between a true image editor and a simple application for dummies. It also includes infinite undo/redo levels, filters, painting tools and artistic affects.
Paint.NET's best characteristic is its interface. Since the first version its visual has been modified, merging the ease of use of simple editors, like MS Paint, with powerful editing tools found in programs like Corel Photo Paint.
Paint.NET can replace MS Paint as the software used when we choose Edit option, after right-clicking an image. It is a lossless change, because Paint.NET is almost lightweight as its Windows counterpart, but includes much more features.
One of the deficiencies of the program is that it can't natively open files in formats like Photoshop's PSD or Corel Photo Paint's CPT. To continue editing a layered file started in one of these programs, user must save each layer separately or else use a third party plug-in, which converts PSD files, with some limitations.
Layer editing is a bit primitive. It isn't possible to create Adjust Layers, for example. Also, there's no way to view two or more images at the same time in the application window. For those who want more features, the program supports plug-ins, with about 140 of them available in the website. Paint.NET is completely free (gratis) e open source, although it uses MIT License, instead of GPL.
BOX:
Paint.Net 3.36
dot.PDN
- Pros: Includes layer support, an uncommon feature in free image editors
- Cons: Doesn't allow viewing more than one image at the same time in the screen
- Conclusion: An image editor, that helps the user doing the basics when messing with photos
- Technical evaluation: 7.6 *
- Price: Free
-
Hey, MadJik,
Very nice plugin! Thank you.
Just one thing: I think "Transparency of the curl" and "Back transparency" are misnamed.
Something with "0" transparency is "completely opaque", so your logic is inverted.
IMO, those options should be "Opacity of the curl" and "Back opacity".
Anyway, great work. Congrats!
-
Hi, Curtis
I've got one crash too. Here's the log:
File: C:\Arquivos de programas\Paint.NET\Effects\CurtisBlack.Effects.dll Effect Name: CurtisBlack.Effects.ChannelMask.ChannelMask Full error message: System.InvalidCastException: Unable to cast object of type 'System.String' to type 'PaintDotNet.Effects.BackgroundEffectRenderer'. at PaintDotNet.Menus.EffectMenuBase.<>c__DisplayClassa.b__8(Object sender, EventArgs e) at PaintDotNet.Effects.EffectConfigDialog.OnEffectTokenChanged() at PaintDotNet.Effects.EffectConfigDialog.set_EffectToken(EffectConfigToken value) at PaintDotNet.Menus.EffectMenuBase.RunEffect(Type effectType)How to reproduce it:
1) Run ChannelMask once. Everything goes well;
2) Run ChannelMask again. Crash!!!
Info:
- I'm using WinXP SP2, Paint.NET 3.31 and the latest version of your plugins (7.2)
- I normally use PDN in pt-br locale, but the error occurs no matter the language PDN is set to.
Thats where all the images, strings and the rtf file that is used for the equations help dialog are stored. Its also there so that people can make their own translations, but I haven't posted how to do that yet.I'd be very happy, if tell me how to do it :-)
I could make a translation to portuguese, like I did with Toli's plugins.
-
Alright. Old tutorial, new idea, a good cause...
Let me introduce you "Stop Global Warming" wallpaper.
Stock image taken from here. All the rest, pure PDN, as usual.
Click on image to get hi-res version from deviantArt:
Both Standard and Widescreen versions provided.
Enjoy! And leave your comments!
-
I'm a big fan of MediaMonkey audio player and some time ago I created a series of wallpapers to match the visual of the new MediaMonkey 3 skin.
These wallpapers were originally published in this post, on MediaMonkey's forum.
Except for the Monkey logo (which was used with permission of MediaMonkey creators, of course), all graphical elements were made from scratch using Paint.NET. Even more: I've put all of them in one single layered PDN file (3.95 MB). This way, anyone can create custom MediaMonkey wallpapers.
Click on the thumbnails to see a bigger version or to download hi-res package from deviantArt:
#5 (the last one) is my favorite. It was built entirely in Paint.NET and it took me a while to recreate that orange orb in hi-res, having only the original small orb from MM skin as a reference.
BWT, if you follow the link to the MediaMonkey forum post, you'll notice I advertised Paint.NET a lot there!!
-
My attempt. Pretty simple I know...
Pure Paint.NET, no stocks.
-
I've got this "Make sure you aren't missing..." error too. PT-BR locale...
-
-
From codelab thread:
NEW IN 3.2- When a standard Effects submenu is used (for example Blurs), effects made
with CodeLab will show up in the localized menu when running Paint.NET
in a localized mode.
Boltbait, now that CodeLab has this capability, could you please rebuild Channel Blur Plugin.
I'd rebuild it myself, but unfortunately you didn't provide the sources
My Effects menu is a little messy with lots of duplicate localized/unlocalized submenus. That's why I'm asking this...
-
Hi, Toli
I've got one bug report and one contribution for your plugins:
1) Bug report: If Paint.Net is running in localized mode, Mirror / Rotate Menu doesn't default to English, in case it misses translation strings for current language. Menu appears blank. That's the case for Portuguese, for instance. See screenshot:
2) Contribution: I've translated your plugins to Portuguese. You can include this in next build if you want.
;Engrave / Emboss [pt] PluginName=Criar Entalhe / Relevo HeaderLabelStyle=Estilo ButtonEngrave=&Entalhe ButtonEmboss=&Relevo HeaderLabelWidth=Profundidade LabelWidth=pixels ButtonOK=OK ButtonCancel=Cancelar ;Mirror / Rotate [pt] PluginName=Espelhar / Girar seleção ButtonWidth=80 ButtonNone=&Nenhum\\(Cancelar) ButtonRotate90=Girar &90° ButtonRotate180=Girar 1&80° ButtonRotate270=Girar 2&70° ButtonHorizontal=Espelhar na\\&Horizontal ButtonVertical=Espelhar na\\&Vertical ButtonFirstDiagonal=Espelhar na\\&1ª Diagonal ButtonSecondDiagonal=Espelhar na\\&2ª Diagonal ;Mirror / Rotate Menu [pt] SubmenuName=Espelhar / Girar seleção Rotate90=Girar &90° Rotate180=Girar 1&80° Rotate270=Girar 2&70° Horizontal=Espelhar na &Horizontal Vertical=Espelhar na &Vertical FirstDiagonal=Espelhar na &1ª Diagonal SecondDiagonal=Espelhar na &2ª Diagonal ;Smooth [pt] PluginName=Suavizar
Cheers
-
As a coincidence, I have been developing similar plugin for some weeks.
You can try this "draft" version: Link
(it is not yet fine enough to be published in plugins section)
Hi, Tanel, I've made some quick tests. Your plug-in looks really promising. Keep the work going!
I noticed, though, it doesn't keep shadows, just like the curves+ method I used above.
I his original post, agent007bond says:
Basically I should be able to remove the background colour (of my choice) and go back to the transparent version (top left) without losing shadow and translucency (partly transparent pixels at edges).Do you think it's possible to implement this (without too much work, I mean)?
-
By finding a method that works when using standard tools, we can automate that into a plugin.
This process is not a waste of time.
So I've made some tests using Curves+. See screenshots below.
As you can see, in Advanced mode, using Hue as input and Alpha as output gives an almost fair result (finding correct hue in the curve is a bit tricky, though).
Problems:
- shadow isn't preserved at all
- edges aren't that smooth and retain some artifacts of background color
So, this is not a real solution, but I think it can be a good start.
In the third picture, I used another approach. With white background, I used Luminosity as input with a completely different curve.
(I know, white is never used as background for chroma-key. Take it just as an exercise :wink: )
See that shadow is preserved in this case, but it's fully opaque. Not what we want...
Note: if you think images are too big, I can replace them by thumbnails.
-
I agree. For me it's more a side effect than a proper feature... :wink:The current function seems more like an undocumented feature.
Nobody would. That's why it took me more than two years to discover it :shock:I wouldn't expect changing the opacity of the color to affect the edge "crispness" of the clone stamp brush....seeing as it's not intuitively obvious that one(Clone Brush "Crispness") would affect the other(Color Transparency).Good point... Simply adding that slider to Clone Stamp would give us a reverse side effect of changing primary color transparency...
So, what's the better solution, in short terms, after all?
Maybe documenting current feature in Clone Stamp help page would be a good start...
-
Sorry, barkbark00
I didn't get your point. In the post you quoted above, the guy is asking for customized brush (a feature that it's not implemented yet, but is indeed a popular request), while in this one, I'm asking for Rick making an already implemented feature more discoverable (like he's doing to other tools).
That's why I thought this wouldn't fall under "Popular Feature Requests", thus deserving a new thread...
Edit: ops, Stephan was faster than me
-
Hey, what a relief! I'm not the only one who missed this
Well, just for comparison, I took a screenshot of corresponding tool in Paint Shop Pro 9 (the last version I used, before it got bloated*).
Note it has two sliders to control this: Hardness and Opacity.
I feel Paint.Net does a combination of both, but it's more like Opacity, although Hardness or Crispness could be good names too, IMO.
* Due to Paint Shop Pro being bloated I discovered Paint.Net, so I really thank Corel for screwing it up!
topic>
-
Today, after more than two years (!!!) of almost daily use of Paint.NET, I discovered "by accident" that Clone Stamp tool :CloneStamp: has the ability to clone areas using smoothed/soft edges (as described in this post) just by changing the primary color transparency.
I always wanted this feature and it has been there for a long time! It just wasn't easily "discoverable".
Before, all I could get with Clone Stamp was something like this:
Now I can easily get this:
So, my suggestion is to add a new Opacity slider to Clone Stamp toolbar (like it's being done to other tools in v3.20) in order to "increase the discoverability of this feature" 8) :
paint.net 4.0 alpha build 5034
in Preview Center
Posted · Edited by gege
Localization BUG:
Apparently, the string used to log layer opacity changes in the History is made by simply concatenating the strings 'Layer' and 'Opacity'. I got to this conclusion by searching the entire .resx files (both: english and pt-br) finding no trace of 'Layer Opacity' or its translated couterpart 'Camada Opacidade'.
Although the concatenation solution does work in english, it may not work for other languages. For instance, in portuguese, the correct translation in this case would be 'Opacidade da camada'. Probably other latin languages like spanish, italian and french will have the same issue.
Edit: I just found out the same applies to other layer properties, i.e., Layer Name, Layer Visibility and Layer Blend Mode