Subj : RE: create new message template To : All From : DAVE GOURD Date : Thu Jan 31 2019 19:17:14 Date: Sun, 25 Mar 2007 01:12:56 -0400 From: DAVE GOURD To: HECTOR SANTOS Subject: RE: create new message template Newsgroups: winserver.public.gamma.testing Message-ID: <1174803176.40.1174783810@winserver.com> References: <1174783810.40.1174780906@winserver.com> X-WcMsg-Attr: Rcvd X-Mailer: Wildcat! Interactive Net Server v7.0.454.5 Lines: 82 One of us misundersttod I think, probably me ... It wasn't a matter of the difference between post and send - sending the message after composing it is straight forward - there's a button to 'post message', could be send, get it out of here, deliver msg, etc. - the terminology moving the msg wasn't the point. Let me try this - I compose a msg - (partially or completely), but BEFORE I click on 'post', I decide I don't want to send it (or post, have it delivered - the terms could be more or less interchangeable as far as most users are concerned). I personally know what to do - click back, home, logoff, anything but the button ("Post Message" is what I see as I write this) that will send the msg on its way, I know enough to not sit here and look for what to do NOT send the message. But some novice users or otherwise unknowledgeable (?dense?) persons might sit there for hours thinking if they leave this page without erasing the message, cancelling, or somehow resetting the created msg that it might get sent. Maybe if there were a cancel or reset button (or some option along side or built into a confirm prompt) that could be chosen as an alternative. A lot more comfort in cancel or reset - there ain't no such animal as 'unsend'. No biggie, just a suggestion. Got another thing for you however - will post it private. -- Dave (see attached example) On 2007-03-24 7:50 PM, HECTOR SANTOS wrote to DAVE GOURD: -> On 2007-03-24 7:01 PM, DAVE GOURD wrote to HECTOR SANTOS: -> -> > I knew right away what one of my members was talking about when she asked -> > if msgs are sent or not if she decided NOT to send a msg she had composed -> > and did not click on post message. She said it was "a little confusing -> > about how not to send a message". -> > -> > I told her as long as she did not click the post button that it would not -> > be sent. -> > -> > So, maybe a cancel w/window or text block that would maybe state - msg -> > cancelled, and or the current click here to continue reading... -> > -> > wcnav has the red hand button, and "do you want to send -> > before this message before quitting" - y/n/c? confirmation dialog, -> > may along that line. -> > -> > -- -> -> Yes, I understand the valid point. But I do have a deja vu of the -> opposite request and discussion a while back. I think it was either a beta -> version or at some point where we had it say [ SEND ] instead of [ POST ]. -> -> The problem with [ SEND ] is that it might make matters worst if the -> message was not "trully" sent yet. This was the reason why we went as far -> to add two attributes to your posted message. If its an EMAIL, then you -> MAY catch it when redisplaying the message and see a "EXPORTED" attribute, -> and then a few seconds latter, a "SENT" attribute. -> -> But thats for EMAIL where the EXPORTED and SENT attributes apply. -> -> What if it isn't an EMAIL but a local message? Does [ SEND ] make sense -> for local communications? -> -> So its all debatible of whats good or better for users. 1st comment about -> it in the manner years, so I think its pretty good. -> -> --- Platinum Xpress/Win/WINServer v3.1 * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013) .