mrphuzz

I would also like to chime in to agree with the poster. I've read other posts, and often they get pretty snotty. I'm not going to do that. I would like to point out, though, that this really shouldn't be that difficult to accomplish from a programming prospective (being one myself). When I attempt to save a file, this configuration window comes up, and it has values in it already. This indicates the values are already stored somewhere. It should be trivial to add a checkbox that reads "Always use these values and don't show this again"... and in the settings dialog of PDN, have a related checkbox that I can uncheck in order to show the configuration dialog if I desire. If the "Always use..." checkbox is checked, PDN can safely assume that I won't be changing the values, so just use the values that are stored already, and don't waste the user's tie with an unnecessary dialog. Perhaps some people would use this config window every time. Or frequently. Or sometimes. But there are those of us that never use it. Considering the triviality of programming the ability to just use the defaults, I don't see this as being an problem (PDN devs seem to be adamantly against this). Forcing me to have to press Enter twice for every file alienates some users. Allowing those users the option to not have the dialog in the first place alienates nobody... it's the holy "everybody wins" outcome. Re: "I found it pretty easy to get used to typing the file name and pressing Enter twice when I know the settings are already what I need."... yes, that is great, but as a developer myself, I have to be consciously aware that what makes sense to me, the developer, doesn't always make sense to the end user. Anyway, that's my two cents. Have a good day.