Jump to content

benh57

+Premium Members
  • Posts

    807
  • Joined

  • Last visited

Everything posted by benh57

  1. Also, minor bug: the 'automatically' checkbox shows up ono PQ Google Map page, but does nothing. (since there is no 'refreshing' for PQ google maps views) And there is no way to enable/disable the disabled icons or white circles on the PQ Google Map page.
  2. The forcing the maps to screen-height only (disallowing scrolling) can actually give you slightly less map height on smaller screens, because with a big map and the scroll bar, you can scroll down half an inch to 'gain' the ~100 pixels of header space at the top of the screen. Personally i'd keep the 3 'map size' buttons, while adding a 'release map' button (which zooms the map to how it is in your macro now) while defaulting to what you have the macro doing now. Another request, it would be cool if Pocket Query google map searches displayed the Premium Member Filters box. So i could temporarily filter out various cache types from PQ Google Maps. If that code is on the page and just hidden, you could just un-hide it in the DOM. (or just re-implement it i suppose)
  3. I suspect he is talking about clicking the 'download .loc file' button which appears next to each cache on the nearst cache lists. When clicked and opened, would open in GSAK. He'd then send taht to the GPSr.
  4. Seems pretty clear there is a bug with this 'feature' from the above posts. It sounds like simply scrolling around the map can cause this. (lots of api hits to the db from scrolling it a lot? ) Though i can think of other ways.. For example, one common thing which might look like a bot to a 'limiter' that someone may do is quickly open a bunch of caches from a list in new tabs using shift -click. Firefox also does 'pre-fetching' in some situations... though probably not quickly.
  5. The real issue is gathering up every TB in the area to take to an event. A bit rude, IMO.
  6. Arguable. I would posit that the 10% figure of geocachers on IE6 are likely to be less-savvy-non-premium members. Probably by more than half. And this decision doesn't "cut" them off anyway -- it just means they won't be getting 'the new features'. However, since these users are using a 9 year old broken browser, i'd say they are rather unlikely to care about new whiz-bang features anyway. All in all, the decision makes sense.
  7. This is a great suggestion, and not one i've seen before..
  8. Do they? I haven't seen an official reply on this one. I've seen one by moun10bike in January, and one by opinionate in February. No promise of a fix, not unusual for Groundspeak. Which is why I respond to these threads to keep the topic fresh Weren't those from before the most recent bug? I find it odd that Jeremy hyped the improved communication from the developers, yet they continue to ignore repeated threads about some issues. I don't think the message got through to the staff.
  9. Do they? I haven't seen an official reply on this one.
  10. Well, it's too late, but i just wanted to reitereate the above advice which was ignored: GET THE 300. The 400T is NOT WORTH IT. The included topo maps are worthless. I'm a 400T owner, btw..
  11. Yes. When you create a new PQ, it will be put in a high priority queue to run a.s.a.p., just as we currently do. We're only talking about adjusting the scheduled PQ start times. Good deal, go for it then. If it's really necessary to get something ASAP then folks can copy and rename one. Of course there are always going to be those that want them NOW ALL THE TIME!! You aren't going to change that behavior. Well while we are updating the PQ system, we might as well add a 'run again' button to be able to instantly run a PQ again which has already run that day. It's silly to have to 'copy' a PQ just so you can run it again. There should be a way to run a PQ more than once, which would of course up the 'run count' on that PQ to 2.
  12. Right!!!! I was right all along. Well no, that's not right at all, since time zones are not straight north-south things. In fact, i can't find a any timezones that don't cross a lot of longitude lines. Map: http://www.worldtimezone.com/
  13. Yeah, just noticed that and updated my post at the same time as you were posting. I'm going to go ahead and delete and relog my last 5 finds without using the field notes, which is going to destroy the evidence. I could also just lock my GSAK record but i tend to use it on many computers, and that's a hassle. Hopeful for a fix soon.. but will probably be til the next monthly update i figure.
  14. 1) GCMAFF 2) I found the cache at 4:03 PM on Saturday, Feb 27, 2010 in the Pacific Time Zone. (Los Angeles) My Oregon's geocache_finds.txt file recorded: GCMAFF,2010-02-28T00:03Z,Found it,"" That appears to be correct, 8 hour offset from LA. 3) I logged the cache via field notes that evening, then noticed the display date on the cache page and in my find list said "Feb 28". So i manually edited the log and changed it to "Feb 27" The next day, i requested "My Finds", which lists this as the date for my log in the xml as Groundspeak:date for log ID # 98355990 2010-02-28T20:00:00Z 4) When imported into GSAK, this cache shows "2/28/2010" as a find date. So, the question is, why does the "My Finds" PQ have a log time which is 20 hours off the time from the field notes file? Also interesting: If you download the GPX from GCMAFF directly, it shows the date for that log to be: 2010-02-27T20:00:00Z So it looks like the database from which the logs in 'my finds' comes from is a different db from which the cache logs come from.
  15. Argh! This bad date comes through to GSAK as well! (via 'My Finds' PQ) GSAK shows the wrong date for those particular finds, even though i edited the log to change the date. I'm gonna have to stop using the 'log' from the field notes page so the bad times don't get sent through the system. -Ben
  16. This all worked fine (in PST) before the last site update which was supposed to fix the date issues -- just made them worse. Extremely annoying. It is nice having the time listed on the field notes page before hand, if only it carried through to the log.
  17. Perhaps the forum search feature Apologies.. Friend hide counts have been broken since the friends feature was introduced.
  18. The strict UTF requirements on this file make editing it a huge pain. It would be awesome if the site accepted the file in any encoding, or just simple ascii text. I've requested this of Groundspeak before, but no word.
  19. Wow! How does that thing get you to the cache, anyway? Does it simply show when you are getting closer or farther away? I can only find one page in English, and that doesn't say much about them. From what I can see, I'd just as soon use a dowsing rod! Um, it's no worse than caching with any iPhone.. it's just a bluetooth GPS dongle that talks to your phone (or laptop). You don't cache with it alone.
  20. Lol... says the party who wants to say who i can and can't marry. Anyway.. this is why caches shouldn't be near houses /residential areas at all.
  21. Well said. There are several boy scout troop caches in LA which have the same issues mentioned in this thread. It's not really anything to do with the BSA per se, just the fact that there is no one person to take ownership.
  22. I still like my G1. I wouldn't want to give up the keyboard. Personal preference. There are literally HUNDREDS of android OS phones coming out, the droid is not THAT special among them.
  23. There are numerous bookmark lists tracking the oldest traditional caches in various areas. But has anyone tracked down the oldest virtuals, puzzles, multis, earthcaches, etc? Would be interesting to check them out..
  24. I agree, would be great. RSS up the site!
  25. I was excited there for a second, but now i say, lame. All reviewer publish logs should be non-deletable. Kudos to the reviewer who is locking theirs.
×
×
  • Create New...