...I agree with this wholeheartedly.

Not because it will solve all of the problems. (gratuitous and predictable posts predicting the idiocy of most humanity except for us omitted here for brevity.) But it is true that many people may click twice because they aren't sure if their clicks registered. If you warn them that there might be a delay, those people who can read will exhibit more patience.

You should still implement other technical solutions (several shown here will work nicely), but you can cut down on a lot of the problems with a simple message to your users. Some of them will see it and they are the ones who deserve to be helped the most anyway.

It's okay to abandon the "us and them" mentality that many programmers and developers exhibit. The people who use our stuff are really part of "us" too. Talk to them instead of trying to be incredibly tricky and saving them from themselves silently. (On the other hand, a safety net is a good idea. And a lot of people won't listen to you when you talk to them. But you take reasonable measures to protect this latter category and then don't worry about them too much.)

---v

In reply to Re: Re: Avoiding a second click by agentv
in thread Avoiding a second click by MMilani

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.