Jump to content

Rick Brewster

Administrator
  • Posts

    20,637
  • Joined

  • Last visited

  • Days Won

    376

Everything posted by Rick Brewster

  1. Paint.NET always shows a GUI when installing with /auto. That's by design, and it's no surprise you're running into problems when trying to run it in a session that prohibits UI. Maybe you want to use MSI-based deployment instead. There are instructions for that in the online help as well.
  2. Maybe if you gave me a description of what you were doing that resulted in this crash, then that would help. The crash log by itself is a smoking gun, but unfortunately not a complete story, and alas I am not psychic*. * yet...
  3. I am unable to reproduce this. (Win7 x64, PDN 3.5.2)
  4. It's in the toolbar ... just change Pixels to Inches.
  5. If you have code which doesn't have access to the property (outside of your Effect class), then just pass it a delegate which it can poll. void OnSetRenderInfo(...) { ... for (y = ...) { if (IsCancelRequested) return; HelperClass.ComputeSomethingExpensiveOmg(y, ..., () => IsCancelRequested); } } ... class HelperClass { bool ComputeSomethingExpensiveOmg(int y, ..., Func cancelPollFn) { ... if (cancelPollFn()) return false; ... return true; } } This is what Auto-Levels does, for instance.
  6. Paint.NET only requires SP2. However, SP3 is recommended and yes I agree that "fully up-to-date" can't be claimed unless you're on SP3... And, SP2 will not be supported for much longer.
  7. The only part of installation that requires an Internet connection is for .NET Framework. Make sure you have 3.5 SP1.
  8. Paint.NET will work with a tablet, but it does not respond to pressure sensitivity.
  9. Being rude to the author (me) is hardly the way to win any support for what you think should be THE NUMBER ONE PRIORITY FEATURES KTHX. If you don't like Paint.NET then by all means uninstall it. I haven't poured 6 years into it just so I could listen to self-entitled junk like this. Thread Closed
  10. They gave you a pretty easy solution. There's no need to be rude and call it "pathetic."
  11. Or it could be as simple as a grouchy network card that's corrupting downloads. True story -- baffled a friend of mine for a straight week once.
  12. You should turn on Microsoft Update. That way, Visual Studio will be automatically kept up-to-date and you won't have to worry about any of this.
  13. This post is over 3 years old. Necroposting is silly. You need to read the rules. Thread Closed
  14. So when do we get a version that responds to IsCancelRequested?
  15. No necroposting. Please read the rules, diegueno. Thread Closed
  16. Yeah this isn't the plugin troubleshooting section. Thread Closed
  17. Tool plugins aren't currently possible. A big theme for PDN 4, however, is extensibility. Not promising tool plugins necessarily -- it's still a long ways out.
  18. I'm not even sure why I still have the splash dialog, honestly. The current behavior is there because I saw the app taking longer to start up when also opening an image (duh ). Now, it's not so important when the app only takes 1 second anyway.
  19. Or you might have been out of disk space, or your hard drive is dying. You should probably check on both (for the latter, do a search for "chkdsk").
  20. selnessongs, You should go read the rules. No necroposting. This thread's been quiet for 3 years. Thread Closed
  21. Sounds like some kind of disk corruption? In any case, why not just rename the PdnSetup directory. Say, call it PdnSetup_
×
×
  • Create New...