Jump to content

fotrik

+Premium Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by fotrik

  1. In about 2013 the page to post new log for geocache was about 1.5 page long on my computer. After the design update by that time (plus minus a year or so) it went above 2 pages. But what you have done is a disaster. The page exploded to 4 pages with plains of white space and extraordinary big characters screaming to my eyes. Thanks for the opt-out (hopefuly permanent!!!) but this doesn't work to field notes!!! Ah yes, sorry, you call it Drafts now... To log ~60 finds last week was one big pain in the a**. You are pushing me to log directly online from Locus with just the predefined TFTC from now on. Maybe with some explanation why am I doing it giving you all the credit. Or are you going to fix it? The old pages are maybe not so nice (they are to me!) but they are efficient. And this is what matters to me.
  2. Hi folks, the event which is niximor talking about is not held in a pub with optional contest and was completely built as a difficult multicache with riddles. Go through the gallery here and you will see the night part of the event. We are going to organize it again and wanted to keep the rules that only the teams who make it (or at least try it) are allowed to log. The event takes half year of intensive preparations, so the only option for us now was to accept that we cannot limit the attended logs anymore but it's good reason not to do the contest anymore or rather do it as unofficial event without the listing next time for those who are really interested to participate. The event was and is D5/T5! It starts at 10 p.m. and ends after 20 hours and is ~25 km long with not only T5 tree climbing stages, the best team did it in 16 hours. Do you think that it's fair if somebody logs the 5/5 rating comming only for a minute to say hi at the finish lane?
  3. You still haven't understood the idea. If I go every month/two months/year to certain location I want to generate up-to-date GPX for the route and another one for the destination. So 1-2 days before the trip I open the PQ settings and activate it to generate the actual data of not found and active geocaches to be able to find few geocaches which are really there and I want the latest coordinates. Then the PQ stays inactive but stored for my next trip when I reactivate it again. I travel a lot to our customers to several places. I want to keep all the PQs for the next visit to easily update the database for the trip.
  4. Read the first post for more explanation!
  5. That's another good idea - to have folders for PQs. ;-) But even 100 or 200 PQs in one list are not a problem if you choose good names, eg. Location: Germany-Koln or Route: Germany-Koln-Frankfurt. I would still welcome the increased limit.
  6. OK, it's just a workaround. If even the deleted queries are stored "forever" then it should be very easy to increase the total number of queries limit without an impact to the HW resources.
  7. I travel a lot usualy the same ways to the same places so I run the corresponding pocket queries once before the trip to update the list of active geocaches. Then I keep the queries inactive (no day of week selected in the query) till the next trip. The problem is that I can't keep more queries than I have now. It would be nice to have more 40 stored pocket queries on the web. The limit of the 5 queries per day is OK but I would apreciate if the number of stored inactive queries is higher, let's say 100. Tomas
×
×
  • Create New...