Dear Money:
What do you mean? If there is undo there is obviously redo.
In most programs, yes, but not all browsers or versions. Even Notepad lacks a Redo ability.
We are seriously listening to someone thats afraid of hitting undo (and can't find the redo button)...?
Redo is Ctrl+Y. In Photoshop, it’s Ctrl+Shift+Y to go back more than one step. I am quite familiar with the Redo command. Don’t assume, or you risk looking like an ass.
By the way, thanks for the
ad hominem abusive. ("This tactic is logically fallacious because insults and even true negative facts about the opponent's personal character have nothing to do with the logical merits of the opponent's arguments or assertions.")
Dear Falkoner:
It's not too difficult to click into your text field, hit ctrl-A, then ctrl-C, I almost always do this before making a long post.
I had already mentioned that in the very post you quoted, just three lines below the text you quoted. I use the clipboard all the time. But in the course of tens of thousands of posts, something is bound to happen.
(Ctrl+A and C to back it up on the clipboard – oops, hit Ctrl-Z! Dammit!)
Dear Devilesk:
A suggestion must be heard before it gets beaten down and beating it down does not stop it from propelling one to think in new ways. Only erasing it completely would do that.
Beating down ideas discourages people from future contributions.
And what you see as "beating down" is considered by others to be valid criticism. Some people want to judge suggestions first before putting them on a list and there's nothing wrong with that.
Matt Burch levied good criticism of the idea.
Another stupid and useless suggestion to add to the already long list of more important things that have yet to be done. Thanks.
This is a prime example of beating down an idea.
Dear Matt:
The main problem with this idea is; If the member you are sending a message to is online, and that member reads it seconds after you have send it, the option for editing the message is gone, and you have to send a new message anyway. Also, if you are editing the message when the recipient begins the read the message, there will be an error message saying that the recipient has already read the message so you would have to send a brand new message anyway.
First off, I thank you for taking the time to discuss the merits and flaws of the idea instead of readily dismissing it. You make several good points. IsolatedPurity beat me to the punch, however, with a potential solution.
Quote from isolatedpurity
edit: oh a possibility for editing is to edit it whether it was read or not, mark the message as new, and include something that says the pm was edited possibly.
I have not seen a site with the option to edit personal messages before reading them, before. Neither have I seen e-mails allowing you to do so. I'm guessing that that is the reason as to why they don't have it; There is a unknown time for editing the message between you sending the message and the recipient reading the message. Although this idea is a little original, I don't really see it being too convenient.
Emails are not a good comparison. PMs here are contained all on the same server, in the same database. Emails are exchanged between often radically different servers outside the jurisdiction of your own email client.
Now to let you know of the current features that are very helpful for this type of situation.
1) There is a "Save Draft" option when you are writing a message. So you can save the message, go do something else, and come back to it. Which is exactly what I did with this post. I wrote it in my notepad, went to work. Then came back for lunch, finished it, and posted it.
Handy, and yes I already know where the button is. Doesn't cover any of those "oops" moments, though, which are pretty much all the advantages I already listed in my previous post.
Save Draft can easily be supplemented with saving in Word or the like, so one could argue even
that isn’t a necessary feature (but it does free you of location and computer). Really only useful when working on a longer post over the course of several sittings, or when interrupted and you need to come back. It does not fill the role of PM editing.
2) There is also a "Delete Sent Messages" feature so you can delete your sent PM's. So that it doesn't: "fill up both people's PM limit faster and causes the 10-history bug to enter the scene sooner." It just fills up the recipients, but the recipient may delete the messages in their inbox too! So I wouldn't worry too much about taking up too much space.
For clearing out space, sure, obviously there is a delete button, great for removing frivolous or time-dependent conversations. However, if you're having an important discussion, you may actually want or need to keep those messages. Granted, you can save them in Word if they're really that important, but that has the same disadvantages as saving in Word rather than using Save Draft. I suppose if you really wanted, you could copy all the text and PM yourself one big message (heck, same workaround could be applied to Save Draft – just PM it to yourself first). Point is, many features exist for our convenience. Without them, there are still workarounds, but they are not always pretty. We have them to improve this community and boost its attraction as a place to relax or work.
I don’t want to waste DiscipleOfAdun’s time sorting through more PMs than necessary because I thought of more FireGraft ideas to add. If possible, I would love to be able to simply edit my first message rather then send multiple supplementary messages.
(Also, don't forget about messages that may need to be kept as documentation or proof, where outside the database any evidence becomes less reliable.)
Dear IsolatedPurity:
Quote from IsolatedPurity
actually today i sent a pm and then i wanted to add stuff after i sent it ;o
Heh, exactly. Until the desire or need is experienced, it’s not likely someone would fully appreciate the prospect of this idea. If I were to have suggested a Save Draft feature, I’d predict the same kind of arguments, simply because it’s a specialized tool.
Quote from IsolatedPurity
and there is nothing wrong with beating down / criticism, however, usually it isn't always that
Criticism is one thing, beating an idea down is another. If you do value suggestions, you must understand the effects of destructive criticism on further contributions from members.
In this particular case, Devilesk was blatant with it ("thanks for another stupid idea"), and Corbo was unjustified because it resulted from the wrong motive (his false dilemma). Nonetheless, to maintain context, keep in mind my original comment was meant for general application, not this thread specifically.
As a developer myself, I don’t care how big my list of changes gets, I’m always interested in hearing new ideas. I may not use any of them, but that’s not what is important. Ideas stimulate the mind, propelling you to think in new ways. I wouldn’t trade that experience for anything. No, what is truly stupid (to use Devilesk's favored word) is beating down a suggestion.