Jump to content

LazyLeopard

Members
  • Posts

    326
  • Joined

  • Last visited

Posts posted by LazyLeopard

  1. If folks want to dress up their cache descriptions that's fine by me, but if I can't read the thing then I'm unlikely to bother trying to find the cache.

     

    Auto-play sound or music is a really bad idea. (How can I quietly browse the site from my office PC if it's likely to start squawking at me at any moment... ;P )

     

    At least JavaScript doesn't get into cache descriptions any more. icon_wink.gif No longer can visiting a cache description cause the browser to fall over in a heap or spew garbage all over the screen... :rolleyes

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  2. I'd much rather a cacher just took a bug home again than leave it at a random location, not in a cache... One of my bugs apparently flew the Atlantic recently, both ways, and ended up back in the cache from which he came. I'm much happier that he logged an extra zero miles and is safe than I would have been if he'd suffered the sort of fate some of those mentioned above have suffered...

     

    When a bug won't fit in a cache I tend to log the bug at the cache and immediately re-grab it, giving the reason (and then take it with me on my next hunt), because at least that way the bug is collecting a story from its visit.

     

    Bugs that make frequent hops are definitely more interesting to follow. One mile travelled today is worth more than a thousand miles promised (but not yet delivered)... ;

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  3. It'd be more informative if the site let you tick boxes that apply, rather than just picking the nearest.

     

    To my mind there's a big difference between a true multi-cache (where there are several locations to be found before the cache is solved) and a series of related caches (where each component is a single cache in its own right).

     

    I'd say that (to pick examples at random) Tomb Raider is a true muti-cache, but the Cluedo caches are a series of single caches, with the final being a mystery cache (because you have to find the others to determine its location).

     

    Whatever

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  4. I'd like to see a distinction between bugs currently held and bugs which have subsequently been placed. That'd give something like "Owned/Held/Moved" rather than "Owned/Found".

     

    The "Held" count would list all the bugs currently in your hands, including ones you own but havn't yet released. The "Moved" count would only include bugs you'd actually put back into a cache, or passed to (been grabbed by) another cacher.

     

    ...and on the other matter, isn't it perfectly possible to add a note to a bug (if you have its tracking number) without actually grabbing it? Or maybe an alternative option could be "I spotted it!" that would do everything "I have it!" does except actually transferring the bug?

     

    Purrs... LazyLeopard [url=http://www.lazyleopard.org.uk]http://www.lazyleopard.org.uk[/url

  5. icon_rolleyes.gif Sometimes folks put bug tracking numbers into their cache log entries. Anyone reading one of those cache log entries could use the tracking number to grab a bug, even though they don't posess it. This is not good...

     

    Morseman grabbed two bugs he's never actually laid hands on because their tracking numbers had been typed into logs for caches he owns. Being a decent bloke, he replaced the bugs in the caches they came from, and wiped out the log entries containing the tracking numbers. Other folk might not have been so kind...

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  6. icon_rolleyes.gif Sometimes folks put bug tracking numbers into their cache log entries. Anyone reading one of those cache log entries could use the tracking number to grab a bug, even though they don't posess it. This is not good...

     

    Morseman grabbed two bugs he's never actually laid hands on because their tracking numbers had been typed into logs for caches he owns. Being a decent bloke, he replaced the bugs in the caches they came from, and wiped out the log entries containing the tracking numbers. Other folk might not have been so kind...

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  7. quote:
    people who add incorrectly formatted HTML in their cache descriptions sometimes cause problems
    I'll check that next time it crashes. One of the descriptions that crashed my Palm did definitely have garbled characters (presumably something non-standard, like smart-quotes) in its title, but this doesn't seem to be a guaranteed indication of problems ahead.

     

    Another thing I've tried, with some success, is to split my search into smaller areas. Appears to help.

     

    quote:
    I'm working on ways to strip poor html but it's not a fun task.
    Good Luck! icon_smile.gif When you get it working, please can you add it to the cache-description editing page script too, so that the bad stuff never gets in? icon_wink.gificon_wink.gif

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  8. quote:
    people who add incorrectly formatted HTML in their cache descriptions sometimes cause problems
    I'll check that next time it crashes. One of the descriptions that crashed my Palm did definitely have garbled characters (presumably something non-standard, like smart-quotes) in its title, but this doesn't seem to be a guaranteed indication of problems ahead.

     

    Another thing I've tried, with some success, is to split my search into smaller areas. Appears to help.

     

    quote:
    I'm working on ways to strip poor html but it's not a fun task.
    Good Luck! icon_smile.gif When you get it working, please can you add it to the cache-description editing page script too, so that the bad stuff never gets in? icon_wink.gificon_wink.gif

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  9. Ok, those of you who have no problems, can you please let on a few pertinent details, like which version of which reader you're using on what PDA, and how many caches (on average) your .prc file contains.

     

    I've installed three .prc files so far, each containing listings for 200 caches, and every single one of them has crashed MobiPocket 4.4 within 3 minutes of my starting to read it on my m105. It's paper-clip time every time.

     

    Are there any other readers that'll run on a Palm m105 and handle the .prc files?

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

  10. Ok, those of you who have no problems, can you please let on a few pertinent details, like which version of which reader you're using on what PDA, and how many caches (on average) your .prc file contains.

     

    I've installed three .prc files so far, each containing listings for 200 caches, and every single one of them has crashed MobiPocket 4.4 within 3 minutes of my starting to read it on my m105. It's paper-clip time every time.

     

    Are there any other readers that'll run on a Palm m105 and handle the .prc files?

     

    Purrs... LazyLeopard http://www.lazyleopard.org.uk

×
×
  • Create New...