Jump to content

TinSoldier

Members
  • Posts

    158
  • Joined

  • Last visited

Posts posted by TinSoldier

  1. Ya I did that. But when I open up paint.net and try looking for it then I don't know where it is located. Could you let me know? TY :) Star*
    It should be under the file menu. You can now open and save as .ico and .cur format.

    Note: I don't see it as anything separate; just when I go to File-->Save As.. then I get the option to save as *.ico in the dialog box.

    Also, like one of the first posts says, make sure it is under the FileTypes folder and not the Effects folder in your Paint.NET directory.

  2. When I open a program to work with it, I do not want to be told that if I want to use it I have to go on line RIGHT NOW and download a newer version. I had no idea it was going to do that. If this happens again I will just say to hell with it. I can't rely on things that will suddenly stop functioning with no warning. How about cutting that BS? Sure, I want to know that there is a new one, but it is damnably arrogant and rude to force users to update.
    Which version are you using? This can be turned off.

    In Paint.Net 3.0 beta (which it sounds like you should not be running) go under the Help menu-->Check for updates-->Options and turn off Automatically check for newer versions of Paint.NET.

    Under 2.72, go to the File Menu-->Updates and uncheck "Automatically check periodically". Also uncheck "Check for Beta releases".

    That should solve that problem.

    One other aggravating thing - the history delete confirmation. It is a royal pain. There should be a way to limit the history as well, so it doesn't have to be policed constantly. Other programs have more user configurable options.
    I don't have a solution for this, but I don't really have a problem with it either. Maybe someone else can help.
    I was very interested in P.N, but could not try it until very recently when I was given a newer computer. It took a lot of effort just to get the program. I had to use someone else's DSL to download the blasted dotnetcrud. DL-ing P.N on dialup can be like rolling a rock uphill too. Then I get slapped in the face.
    Few things worth downloading from the internet anymore are worth downloading without broadband. Other than buying a commercial tool, I don't see a good solution for this problem either. .NET is required for a lot of things anymore, in the Windows world.
  3. I read your first post and I believed that I had a solution. Instead of merging down the top layer onto the shadow layer, why not merge the shadow layer down to the background?

    I tested it and it worked:

    road-inset.jpg

    I didn't have the same images as you did so I had to make do. Note: I feathered both the shadow and the inset image before flattening them and I set the shadow to 192 transparency instead of 128 because of the darkness of the pictures.

    Edit: I didn't try different blending modes...

  4. So at 144dpi I'm staring at 384x384 thumbnails and wondering if that 30" Dell monitor isn't as superfluous as I thought...
    Now I'm jealous! I was happy to have a 19 or 20 inch LCD at work. 30 inch?!? Gaah!

    But I don't do graphic work, so I guess my monitor is good enough. I do have to look at PDF electronic schematics though. It helps.

  5. I wasn't sure what you meant, so I tried it myself.

    Using Paint.NET 3.0 beta 2 and the built-in clouds function.

    I set the primary color to transparent and the secondary color to white. It worked just fine for me. I got white clouds against a transparent background. Edit: I guess that may seem a little backwards, but I figured it out with a little bit of experimentation.End edit.

    It also works for me using the plugin.

    Maybe you should post a picture after all?

  6. I don't see any changes in the color version...

    Maybe in the grayscale version, the there are 256 shades of gray that make up the picture in the first frame. In the second frame the program has to use one or more palette entries for the red color, thereby reducing the number of grays available.

    If those palette entries were blank and unused in the first frame then you wouldn't notice the flicker. If both frames used the same palette, the flicker would go away.

    That's my theory, anyway.

×
×
  • Create New...