gege

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

2

About gege

  • Birthday 01/21/1972

Profile Information

  • Gender
    Male
  • Location
    Brazil

Contact Methods

  • Website URL
    http://paintdotnet.forumer.com/viewtopic.php?f=26&t=23653
  1. 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
  2. Hummm... I thought it was a thousand...
  3. 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.
  4. I don't think it's a bug. It's "undocumented behavior"! Well, now it's documented, so... whatever.
  5. 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.
  6. 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).
  7. 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
  8. 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.
  9. 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.
  10. 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 * FYI, Photoshop CS4 received 9.0 from the same magazine.
  11. BTW, Aviary has a GREAT tutorials section! It's worth to take a look.
  12. http://www.mechcad.net Hum, AceMoney website... anyone in need of putting finances in order?
  13. Ditto! I already did it. It's like having a local app indeed.
  14. Did anyone notice pixlr.com? I've made a forum search and didn't found any mention to it, so I thought it was worth to share... It is a free online image editor, made completely in Flash. Its interface is very elegant and polished and tries to mimic Photoshop's. Regarding features, it is far from Photoshop or even Paint.NET, but it has the basic functionality, including some filters. Can be useful for some basic adjusts, if you don't have a local editor installed. In fact, at least ONE feature is far superior compared to PdN: BRUSHES! ;-) And there's also some Tools, which PdN misses: Dodge, Burn, Smudge, Sharpen, Blur... (Please note: I mean 'Tools', not 'Filters'/'Effects'). Of course, I won't give up Paint.NET, but I'll keep the URL just in case...
  15. 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!