configurable behavior for "save changes?" behavior

Ideas for new features

Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard

Post Reply
kisrael
Posts: 4
Joined: Wed Apr 09, 2003 2:12 pm

configurable behavior for "save changes?" behavior

Post by kisrael »

Sometimes the behavior of "save Changes?" on program close drives me nuts...

1. Often I use textpad for a quick cut-and-paste-and-cut (to cleanse the palette of any formatting, so to speak) -- here's a hint. If it's a blank window named "Document#"...I DON'T WANT TO SAVE IT.

2. Actually, I'd like a way of saying "save all documents w/ a named file" and the option to "throw away all windows w/ no file" or "put all non-blank documents w/ no file in a configurable scratch directory".

Those changes would make life friendlier...I especially hate when Textpad's "save changes?" interrupts a windows shutdown
kisrael
Posts: 4
Joined: Wed Apr 09, 2003 2:12 pm

Post by kisrael »

Heh. I was thinking about posting this idea, but then realized I might've already posted it...as indeed I have.

I just get so sick of being asked if I want to "Save Changes to Document1?" It's ALWAYS one extra step from what I want to do. I like the idea of prompting to save changes for named files, but for DocumentX, which is often just a scratch space, it's an annoyance. (My previous suggesting for a "save all unnamed files in scratch area" still seems like a decent compromise to preserve data without breaking workflow and the blocking the shutdown procedure.)
Post Reply