Jump to content

Nick Hanson

  • Content Count

  • Joined

  • Last visited

Community Reputation


About Nick Hanson

  • Birthday 01/01/1970

Profile Information

  • Location
    Fredericksburg, VA (USA)
  • Interests
    Washington Capitals Hockey, VA Tech Football, Computers, Politics

Contact Methods

  • Website URL
  • ICQ

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. *bump* Perhaps I missed a more recent post stating this feature was no longer going to be implemented (it is a rather old thread) but as of this thread the indications seemed to be the feature was "coming soon". Not only did it not make it into v2.6 (as expected) it didn't make it into the 2.7 series either nor has it made it to v3.0. For whatever reason a fair number of games I play only output screenshots (using the in-game mechanic) in TGA and it would be really nice to be able to see what the heck these things were without having to open each one.
  2. With the two radial control blocks in the bottom corners it gives me the impression that it's made for a handheld device and those are for use with your thumbs. I think MS has a touchscreen keyboard that is split into two radial sections in the bottom corners like that for use on the UMPC or whatever the heck that handheld computer thing they're selling is called.
  3. You're assumption is incorrect. We have MINIMAL say in when we can upgrade the OS on our corporate desktops. That decision has already been made by others and we won't be getting rid of Win2k till 2008 at the earliest. We DO have a lot of say in what applications we use to do our jobs. There are restrictions of course: budgetary, legal, as well as policy. Budgetary is fine with Paint.Net 'cause it's free (beer). Legal is fine with Paint.Net because the license permits its use. Policy is fine with Paint.Net as long as we standardize on it and each dev isn't using a different app or version. We'
  4. I have no idea what this means. What question stands? It makes no difference at all to us that Windows 2000 is developed or supported. We're developers. The OS is supported by the Systems/Networking people (not us). Likewise it is their decision, NOT OURS, on when we can upgrade the OS. If it was our choise we'd upgrade the second Vista came out but then we don't have to deploy or support it either. They've decided we aren't upgrading to Vista till 2008 or so and thus we have a problem with a tool we using being unsupported until then. Since the source is available and we are developers a fork
  5. I'm not sure what you're asking here. If you're asking why someone who is unwilling to upgrade from Windows 2000 to XP or Vista need to upgrade to Paint.Net 3+ then they don't. It's not possible. Paint.Net 2.x runs just fine on Windows 2000 though and when Paint.Net moves to 3+ all those users (which is admittedly a TINY percentage of the overall Paint.Net user base) will have an unsupported and no longer developed piece of software. Well you're probably not a programmer either. In my situation I have an installed user base who uses a tool that is going to (has?) become unsupported. The use
  6. First let me say I didn't mean to imply that I beleived the direction you are going is not correct. I believe you are doing the right thing for the future of Paint.Net in moving to newer technology that the user base will all eventually migrate to. The point of the fork would NOT be to draw users from Paint.Net, I don't see it competing with Paint.Net at all because it's specifically targeting users that you no longer support. That said I represent a group of people that still have many Win2k systems (primarily in corporate environments). I already KNOW my user base and I'm sure it's a TINY f
  7. Rick, First let me say this is just a general inquiry not a statement of intent. That said since v3.0 no longer supports Win2k and never fully supported it (printing/scanning) and I assume the 2.x series will no longer be developed what are your feelings on having your project forked? More specifically: The idea would be to take the source for the last 2.x version and use that as the basis for a project. The main goal of the project would be to continue supporting Win2k, expand that support to possibly include printing/scanning, and potentially even try to rework some things to make a mono v
  8. Any of you Firefox fans following the IceWeasel issue? I'm just curious what others think of it. For those that don't know: The Mozilla Corp. decided that the Debian Linux distribution can no longer distribute Firefox under that name without including their non-free logo and artwork and submitting all patches to Mozilla for approval before release. Debian has a social contract that prohibits them from distributing non-free items that forms the whole basis for their distribution. They previously had an arrangement with the Mozilla Foundation that allowed them to use the name without the non
  9. The CSS support is MUCH improved (though still not as good as either Firefox or Opera.) The security features are GREAT. I like how it handles RSS much better then Firefox. The Quick Tabs are a great feature. All that said I HATE the UI. I was hoping it would grow on me but I've been using it since the first public beta and I still HATE it. So much so that I'm probably going to get a 3rd party browser that uses the IE engine just because the UI is so painful for me to use. I can't believe usability studies said this thing was good.
  10. I'm confused. Doesn't the Donate button on the website go to Washington State University? Does this OneCare ad revenue go there to? Do they want more money to host or something? If you would like to derive money from Paint.Net (which is reasonable consider how much time/effort you put into the project) why not just make the donate button funds go to you (and your fellow developers) instead of Washington State University?
  11. Just select the area you want to crop and use crop to selection. If you want to move it around just use move selection.
  12. Just out of curiosity what is involved in writing a basic plugin? Is is as simple and either inheriting from a Paint.Net plugin base class or implementing a Paint.Net Plugin Interface? Are there a bunch of nice C# methods a plugin writer can call and events we can bind our code to? Or is it lower level with a ton of PInvokes, COM Interop stuff, and/or custom attributes and such. I'm curious because if it's anything like the first two I might give it a try once there is some documentation but I have no interest in manually searching through the source code of the whole app for how to hook s
  13. I'm curious, I don't have any mult-page Tiff files handy but if I recall correctly my old fax software used to recieve faxes as tiffs and all the pages were in a single tiff. Does anyone know if Paint.Net supports multi-page tiffs (perhaps each page as a layer) or does it just load the first page?
  • Create New...