Rick Brewster

Administrators
  • Content count

    14,399
  • Joined

  • Last visited

  • Days Won

    89

Everything posted by Rick Brewster

  1. I haven't actually had the chance to look into it yet.
  2. Hmm ... I would give it a 6/10. I thought some of the emotional responses were way too dramatic and forced. Cool story idea, really good visual presentation, but it seemed like someone said "You know what would make this movie better? Dumbing it down for teenagers with some poorly developed emotions and love stuff." And by "better" they meant "sell better". (I understand the business rationale. That doesn't mean I have to enjoy the result ) Also, here's a BIG HINT to anyone who may want to watch this: DO NOT WATCH THE TRAILER. Just go watch the movie. Go in with zero knowledge and expectations. The trailer spoils some important aspects of the story's development. Despite my criticism of it, it was worth the $5 rental on Amazon Prime.
  3. You're welcome :-D
  4. I believe this only happens for Rectangle
  5. You need to run chkdsk -- something on your hard drive got corrupted. Chkdsk is usually pretty good at fixing it though.
  6. Have you tried turning off antialiasing in the toolbar?
  7. Glad it works again I totally understand the stress -- I've had games or electronics that would occasionally suffer a reoccurring "twitch" or glitch of some kind that was impossible to figure out. It just adds anxiety to an otherwise enjoyable experience. It's a little like living next door to a dog that likes to randomly bark really loud.
  8. Do you have a lot of (or any) plugins installed? Anyone else having problems like this on a Core i3? Or any other dual core systems
  9. Did you want more ... or less?
  10. Unfortunately that won't work well unless you're also switching between Normal and Overwrite blending modes
  11. It's not.
  12. https://blogs.msdn.microsoft.com/dotnet/2016/08/24/whats-new-in-csharp-7-0/ C# 7 features that sound really compelling to me: Local functions!!! These were in Pascal since the early 90s at least, when I used Borland Turbo Pascal 4.5. Sooooooo useful Throw expressions, e.g. "return value ?? throw new Exception()" ... this is really really really the right syntax to have! Ref returns and locals ... this would have been useful at some point although I forget exactly where "Out variables" ... it's a small improvement but it will help!
  13. Well, it works now at least
  14. You've listed any number of bad pieces of hardware, and several dubious strategies, that are easily culprits here. A dying hard drive, a replacement but "on sale" hard drive (really bad idea!), a super old AMD motherboard with bad GPU drivers, trying to run the installer in compatibility modes, trying to install in safe mode and getting bizarre errors, etc. I think your computer is just broken. Until you fix replace the hardware, trying to get software to cooperate is just going to continue to be a monstrous waste of everyone's time.
  15. You need to run chkdsk -- your disk may be going bad :O
  16. Trump's Twitter account is not something you should study for how to interact with people.
  17. Right now, if you want a specific % when resizing a selection, you'll have to calculate it yourself. Reporting the % in the toolbar would be interesting though, and would pretty much get you the precision you need. Even if it's a bit more manual labor, it's a step in the right direction.
  18. Not a bug. That's intentional. The aspect ratio for constraining is locked in when you first draw the selection.
  19. If there was news, you'd see it here on the forum or on the blog ( http://blog.getpaint.net )
  20. This thread is devolving into fighting. I'm closing it.
  21. This is due to rounding errors based on the size of the invalidation rectangle. It's a bug that keeps coming back everytime I think I've fixed it. But, it's purely a visual artifact and nothing bad is actually happening. The invalidation rectangle is the part of the screen that needs to be redrawn. Those corner handles are fading in and out, but they don't change their appearance on every frame. And the selection outline is animating as well, but it also doesn't change every frame. So sometimes the invalidation rectangle surrounds the whole selected area plus the handles, but sometimes it only surrounds the selected rectangle. And at non-integral (anything other than 100%, 200%, 300%, etc.), you just get rounding errors. And there's some line or two of code that is incorrectly rounding up when it should round down, or vice versa. And it's difficult to reproduce this, and it's difficult to figure out which line of code to tweak, and it's difficult to test to make sure that some other and bigger problem wasn't introduced with the fix. Sometimes the rounding error is worse with hardware acceleration. Sometimes it's worse with software rendering. So, tl;dr ... ¯\_(ツ)_/¯
  22. BTW, here is the DirectWrite interface that handles text layout: https://msdn.microsoft.com/en-us/library/windows/desktop/dd316718(v=vs.85).aspx In particular, Paint.NET makes use of GetMetrics and GetOverhangMetrics quite a bit.
  23. First of all: statements like this should almost always be translated to "I don't understand this and I don't want to figure out why." It's a lazy rhetorical device and it should be avoided. In my opinion. Anyway. I don't think y'all are understanding how text rendering and font measurement stuff works. That's not an insult -- this stuff is actually quite complicated and confusing. Incorrect. If you type in 40 for a font size in Paint.NET, it sends that size over to DirectWrite. DW then grabs glyphs from the font and does stuff. Whatever DW says the measurements are, that's what Paint.NET uses, and DirectWrite is very serious about getting this stuff correct. And the font is VERY much in control of things, too. There are some super crazy fancy cursive fonts that go all over the place, and asking for "size 40" in that case does NOT mean that anything you type will fit into a 40 pixel tall box. That's just not what "size 40" means. And for the Arial example with "The dog", it's 50 pixels tall because the "g" has a descender (as pointed out almost immediately by IRON67). Without that, the text is about 40 pixels tall, although you might see things +/-1 pixels due to antialiasing spillover/under. This is something I've spent a lot of time on to ensure correctness on. There is no bug in Paint.NET here. This is not an "inconsistency" and it's not because "there's only 1 developer" or that "text related inconsistencies aren't a priority for [me]". I promise you that things are correct, and it's only your lack of knowledge that makes things seem "wrong" (and again, even if I sound like a jerk when I say that, I promise you it's not meant to be an insult!). Incorrect. As you increase the font size, your magical "10" will have to increase. As you decrease the font size, you'll have to decrease your magic number. You simply have a discrepancy between what you think you're asking for and what you're actually getting.