pppingme
-
Posts
1238 -
Joined
-
Last visited
Posts posted by pppingme
-
-
Source code from a page on gc.com
<!-- Start Quantcast tag --> <script type="text/javascript"> _qoptions={ qacct:"p-f6VPrfmR4cujU" }; </script> <script type="text/javascript" src="http://edge.quantserve.com/quant.js"></script> <noscript> <img src="http://pixel.quantserve.com/pixel/p-f6VPrfmR4cujU.gif" style="display: none;" border="0" height="1" width="1" alt="Quantcast"/> </noscript> <!-- End Quantcast tag -->So they are doing pixel tracking (a way to place tracking cookies) as well as running some javascript.
As I look closer, this is NOT the only 3rd party tracking they are doing.
-
Potato Finder,
What exactly does this trick do on the Oregon 400 ? Change the screen resolution, contrast or what ?
Thanks, Tim
The default backlight level is just too low to be useful in most situations. It just increases it. My testing and other reports I've found show that this makes little difference in battery life.
-
The logs are retrieved from a database table. The order they are retrieved is defined by the way the datebase query is written. None of that is a Graphical User Interface issue.
Its a simple SQL query that the GUI designer wrote and inserted into their asp code, the very same code that outputs what you see on your screen. It doesn't matter how its in the database, its that sql query that the page designer wrote that determines how and what order things are displayed.
-
Are you running any of those greasemonkey scripts? They can alter the page quite a bit and its possible one of those were messing you up.
-
The Oregon screen looks pretty pathetic.
...
Too bad.... I would really like the touch screen feature of the Oregon.
Tim
Tap the power button quickly (don't hold it), hit the "+" a couple times, enjoy your new screen.
Hi Potato Finder !
I don't have the Oregon 400c ( yet ). But if this is a tip/trick to dramatically improve the readability of the screen on the Oregon.... it may push me over the edge to get one.
I DO have a 76CSx.... will this trick/tip work on that ?
Sorry, I don't know the 60's or 76's, but I know on "some" of the other garmins, if your on the sat screen hitting the zoom in/out (+/-) buttons will do it, this is true of all the etrex's as far as I know, just don't know on the 76 though.
-
Agreed, not a bug, but bad GUI design. Why? Because it's inconsistent and user expects one thing from both interfaces... To be honest, I don't care which way it is, and I understand both POV, but it should be the same on the HTML page and identical on the PQ... Anyway, nothing I can do, too little priority for this to be even considered, I'm sure...
It's not a GUI issue at all, it's a database issue.
Wrong, The GUI is programmed to display logs in order of user date, not order of entry. This is in no way a database issue, its a design decision by the programmer who wrote the cache page.
PQ's on the other hand give the 5 most recent logs, for those that accumulate logs (yes, there is very good reason to do so) this is much more desirable behavior, again, a design decision by the programmer that wrote the code to produce gpx files.
Neither of these is a database issue.
Side note: I accumulate logs because I like to have 10 logs when I'm out searching, 5 just isn't enough.
-
I had serious doubts until I went ahead and bought my Oregon 400t.
Everyone kept talking about the screen. The first unit I held in my hand I thought I had to agree, and the guy at the counter actually told me thats the best it can do.
Fortunately someone else walked up and realized the one I was looking at was fresh out of the box, he told me how to adjust the screen, and I walked away with a completely positive feeling about it. I ordered one online, and I have no regrets and have had no problem with reading the screen, battery life, or any other problems.
-
The Oregon screen looks pretty pathetic.
...
Too bad.... I would really like the touch screen feature of the Oregon.
Tim
Tap the power button quickly (don't hold it), hit the "+" a couple times, enjoy your new screen.
-
I really wonder what the goal of this question is, especially the "without backlight" part.
There seems to be a lot of confusion about this, especially related to the Garmin Oregon and Colorado.
Here's the facts.
Color LCD screens by design look best when they are backlit.
On both the Oregon and Colorado, leaving the back light on permanently actually has very little effect on battery life (disclaimer, if your using old exhausted batteries, there is more of an effect).
On my unit with fresh NiMH batteries, I can get about 18 hours without the backlight (leaving it on my desk, not touching it) and about 16 hours with the backlight locked on. This just isn't enough to even think about.
Read this:
http://www.gpsfix.net/battery-life-compari...egon-and-60csx/
Also read "H8" on this page:
https://garmincolorado.wikispaces.com/Hardw...,+Cables,+Power
I would expect (and I get) similar times on the Oregon.
-
There are a couple things that can cause this, some have been mentioned, but the one that sticks out that hasn't is overcharged batteries.
Yes, the legend seems very sensitive to this, even compared to other etrex units. I used to always have the problem with mine, and when I dumped my charger (for other reasons) and got a good charger, this problem disappeared completely.
Lithium batteries also have a higher voltage and can cause the problem too.
Either way, when you first put fresh batteries in, turn on the unit, and hit the light for a couple minutes and see if the problem goes away.
-
Hmm..
They can run duplicate PQ's that weren't requested yet regularly scheduled PQ's still struggle.
-
I'm currently using a Garmin Legend HCX and am very happy with it. I'm going to be passing it on to a family member and was wondering if the Garmin 60CSx is a good upgrade or should I just get another legend HCX. From what I have read I do not want a Delorme or at this time an Oregon or Colorado.
The Oregon's are a good strong unit, can store full information on caches, and even do simple logging right on the unit, no need to carry a separate PDA or printouts or anything else.
Why would you not want an Oregon (except for the price tag)?
I would agree about not buying a Colorado unless you get a real good price, there are a lot of indications that Garmin may phase this unit out early, so if thats true, software updates for it may not happen much longer.
-
Oregon has sunlight unreadable screen
Why do people keep saying this? I almost didn't buy an Oregon because I kept seeing this over and over, I'm glad I ignored it now. There is absolutely NO problem reading the Oregon's screen in sunlight or any other condition. Out of the box the default settings aren't the best but it takes less than 2 seconds to adjust and its a permanent fix (i.e. doesn't loose it again when changing batteries, etc).
-
What happens after 1000 waypoints? Do you delete them?
I deleted and reloaded all waypoints (caches) every day. I never walked around with data that might be old.
-
I'm considering getting one, I've only found 25 and I plan to get it in June. Should I get it?
GeoShif
I used one for a little over 400 caches and it works just fine.
I would recommend getting the "legend H" for a similar price, its a little more sensitive, but mine was just a plain legend.
Its a decent unit for the price and holds 1000 waypoints. I also used mine and hooked it to a laptop with streets and trips and had in car navigation with that.
-
I recently logged a DNF at cache GC1DX74. I looked at it again today and noticed that under "Logged Visits" that there is no count for DNF (there should be at least 1 DNF - mine!). I'm not sure if this bug extends to other types of logs. I also noticed the same issue in another recent DNF. Anyway, just thought I should report this as it seems to be a bug.
Those numbers don't seem to update real time, I don't know if they update once a day or what, but definitely not real time.
-
I used the Garmin Rino's for a while but the practical distance is far less than what is advertised. With the GRMS - maybe about 2 miles max in average woodland conditions. On FRMS - the average was more like about 300 - 400 yards.
Which model Rino are you using? I've never heard reports this bad (3-400 yards).
-
PQ's do return the last 5 logs, but you should note, it returns the 5 most recently entered logs, NOT the last 5 logs by date.
So, if a person logs a DNF for todays date, then 5 people come along later and enter a found log for yesterday or earlier, then the PQ will not include the dnf, even though its technically more recent and accurate info.
Before arguing that this is a bug, I'll say that I prefer this behavior (and thats a whole separate thread).
-
I think the problem lies in the fact that Garmin may not be responsive in updating the player. Improvements in the Builder are only useful if the corresponding player is updated to take advantage of them.
For PocketPC's, Groundspeak can probably issue both builder and player. They are at the mercy of Garmin for the OR and CO.
But I would hope that Garmin supports the game.
But now the real question, Is gs doing ANYTHING to work with garmin to resolve these issues? If gs changes the format of the cartridges (and its obvious they have, cartridges made with the newer tool don't work on garmins, yet cartridges built on the older tool do).
OR
Did gs release a builder that just puts out buggy cartridges, so there is nothing to fix on the Garmin side?
-
That 4 pin flat connector is only capable of serial (rs-232) communications, not USB.
That being said, you have two choices, you can either get a usb/serial adapter (usually these are short cables with usb on one side and serial on the other) so you use your existing cable, plug that into the adapter cable and plug that into your computer, the second option is really the same, but there are a few cables that have all this combined in one, they go from the flat etrex connector to USB directly.
-
I don't see the Oregon as being "miles" above the Colorado, either.
It appears that Garmin took note of all the problems with the Colorado and fixed them with the Oregon. It seems like from reading forums, people constantly complain about bugs, crashes, etc on the Colorado but most Oregon complaints seem to focus on not knowing how to use the units.
To me a smooth running unit is miles above a buggy unit that crashes or gives significant problems all the time.
-
So I've been a avid 76csx user for years now and had recently looked into getting either a Colorado or Oregon but the cost was to steep even for the amount of ease and features it would add to my geocaching experience. Last night i was browsing my local Best Buy (Gulfport, MS) and found a Colorado 400T for only $319, i thought it must of been a mistake but the sticker read down from $599, oddly enough the 400c was next to it at full price. There was only one on the shelf so i grabbed it up and headed to checkout half expecting for it ring up different and having to attempt to get a manager to honor the sticker price, but sure enough it was only $319 still 180 bucks cheaper than the 300 without maps sells for and 280 bucks cheaper than buying the same model would cost online at say oh i dont know, BestBuy.com. Any who i figured id share in case its like this anywhere else, maybe i just lucked out who knows, if you want to call ahead to check the SKU is 8828664. I just cant wait to try the paperless caching feature out in the field, i know this model has some bugs but at that price who could pass?
That appears to either be a local price or a sale that ended on Saturday. Their website is showing full price.
-
Is there ANY advantage of a Colorado over an Oregon? Why would someone buy a Colorado over the Oregon?
I'm trying to understand why the pricing is exactly the same when the Oregon seems miles above the Colorado.
I'm leaning toward an Oregon but trying to figure out if I'm missing something. I've looked over Garmin's website and read up as much as I can and nothing is sticking out to me.
-
Actually, your both right, and wrong.
The minimum size for searches is set at its default, but IS able to be easily changed by the board admins.
As far as searches slowing down the forums, although that can be true, if it is a problem here its also something that can easily be changed. A time limit can be enforced between searches (say 60 or 90 seconds are usually good settings for a medium sized board).
Pocket Query log contents
in Website
Posted
And I longer than you. Its the "gui designers" call, not the database admins.