LazyLeopard

Yeah, red-backs like to live in piles of dead wood. Definitely need looking out for while you're rummaging through those bushes looking for that box. I'm not keen on the dugites and tiger snakes either.... Purrs... LazyLeopard http://www.lazyleopard.org.uk

The most recent software upgrade for the Vista has raised the waypoint maximum from 500 to 1000, which makes a big difference to my pocket query download use. I used to have things trimmed to the bare minimum. Now I can cover most of the ground for a hundred miles and still have spare space. Purrs... LazyLeopard http://www.lazyleopard.org.uk

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. 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

Yep, sounds like it might be fun, but I'm hobbling at the moment (a victim of Inclined to be Nervous) so I can only visit caches on nice level terrain. I think I'd prefer lunchtime to evening. I have no problems with caching after lunch though. Sundays are marginally less heavily booked than Saturdays... Purrs... LazyLeopard http://www.lazyleopard.org.uk

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

Urk! Double post... This was a duplicate... [This message was edited by Lazy Leopard on September 16, 2002 at 10:12 AM.]

Urk! Double post... This was a duplicate... [This message was edited by Lazy Leopard on September 16, 2002 at 10:12 AM.]

Assuming the information to make the connection exists, how about a TBug icon and link against the log of the visit when the TBug was dropped? That'd spread the list of TBugs throughout the cache log history... Purrs... LazyLeopard http://www.lazyleopard.org.uk

Three of those four choices could apply. The fourth only applies if there's a hard and fast trade rule. I've visited my local Bug Hotel just to collect bugs, and just to leave bugs. The bug population round here just isn't high enough that a hard and fast trade rule could work anyway. Purrs... LazyLeopard http://www.lazyleopard.org.uk

I find switching to OSGB tends to do nasty things to the waypoints that don't lie in the British Isles, especially if I download them from my unit into some program or other, so I always have my unit on WGS. Be nice to see the OS using WGS... Purrs... LazyLeopard http://www.lazyleopard.org.uk

I find switching to OSGB tends to do nasty things to the waypoints that don't lie in the British Isles, especially if I download them from my unit into some program or other, so I always have my unit on WGS. Be nice to see the OS using WGS... Purrs... LazyLeopard http://www.lazyleopard.org.uk

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

I've seen serious spoilers posted in the captions of images. At the moment, if you want to remove the spoilers, the only option is to delete the photograph. An option to encrypt the caption instead would be handy... Cheers! Purrs... LazyLeopard http://www.lazyleopard.org.uk

I've seen serious spoilers posted in the captions of images. At the moment, if you want to remove the spoilers, the only option is to delete the photograph. An option to encrypt the caption instead would be handy... Cheers! Purrs... LazyLeopard http://www.lazyleopard.org.uk

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

Mikemtn added a note to the cache on 17th August to say the bug is back in there... Purrs... LazyLeopard http://www.lazyleopard.org.uk

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

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

Seems to me the problems with bugs here (in the UK) exactly match the problems mentioned in the Travel Bug Forum... :/ Purrs... LazyLeopard http://www.lazyleopard.org.uk

quote:people who add incorrectly formatted HTML in their cache descriptions sometimes cause problemsI'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! 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? Purrs... LazyLeopard http://www.lazyleopard.org.uk

quote:people who add incorrectly formatted HTML in their cache descriptions sometimes cause problemsI'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! 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? Purrs... LazyLeopard http://www.lazyleopard.org.uk

Ack! Knew I'd forgotten one pertinent bit of info. My m105 has PalmOS 3.5.2 loaded. MobiPocket claims to be 4.4.375, and I've got at least 4Mb memory free even after loading the pocket book... Purrs... LazyLeopard http://www.lazyleopard.org.uk

Ack! Knew I'd forgotten one pertinent bit of info. My m105 has PalmOS 3.5.2 loaded. MobiPocket claims to be 4.4.375, and I've got at least 4Mb memory free even after loading the pocket book... Purrs... LazyLeopard http://www.lazyleopard.org.uk

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

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