Pocket Query log contents

[+Beauty & The Beast]

Hi all,

not sure if this has been asked before or not, or there is some obvious answer. Please point me in the right direction if that's the case. I did search through the forum and gc.com website via google. Can't find an answer.

 

Pocket Query - I noticed that DNF logs are not being displayed in the GPX file after being generated by Pocket Query. All the other logs appear to be there fine, just the DNFs... If I click "GPX Exchange File" on the cache, they all come up in the .GPX file, but not if it's ran as pocket query.

 

Is this how it's been designed, or does this not sound quite right???

 

THANKS!!!!

 

B&B

[+Yossarian]

Pocket Queries include the 5 most recent logs. I believe the GPX files on the cache pages include up to the 20 most recent logs. If there are DNFs within those 5 or 20 most recent logs, they should be included. If a DNF was say the 7th most recent log it would be included in the cache page GPX but not the PQ.

[+pppingme]

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

[+Beauty & The Beast]

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.

Interesting stuff. Thank you very much for explaining how it works...

Before arguing that this is a bug, I'll say that I prefer this behavior (and thats a whole separate thread).

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

[+Beauty & The Beast]

Once again, thanks for explaining it to me!

[+Prime Suspect]

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.

[jholly]

 

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

 

Part of the reason is it take lots of resource to generate a PQ, while downloading the .gpx off the cache page is less resource intensive. Since it takes less resource for a page download, you get more.

 

Jim

[+pppingme]

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.

[+Prime Suspect]

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.

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.

[+pppingme]

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.

[+Prime Suspect]

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.

I'm glad you now realize that a SQL call is not a GUI issue. Now, if I clicked on a log's decrypt link, and it didn't work, that would be a GUI issue, because it's an interface element that's not working. Log order has no interface element to it. It can be a tricky distinction. Fortunately, I've been designing and writing applications since the early 80s, so it's not all that hard for me.

[+pppingme]

I'm glad you now realize that a SQL call is not a GUI issue. Now, if I clicked on a log's decrypt link, and it didn't work, that would be a GUI issue, because it's an interface element that's not working. Log order has no interface element to it. It can be a tricky distinction. Fortunately, I've been designing and writing applications since the early 80s, so it's not all that hard for me.

And I longer than you. Its the "gui designers" call, not the database admins.

[+Beauty & The Beast]

I'm glad you now realize that a SQL call is not a GUI issue. Now, if I clicked on a log's decrypt link, and it didn't work, that would be a GUI issue, because it's an interface element that's not working. Log order has no interface element to it. It can be a tricky distinction. Fortunately, I've been designing and writing applications since the early 80s, so it's not all that hard for me.

And I longer than you. Its the "gui designers" call, not the database admins.

Hey guys, we didn't mean to start a flameball. Just noticing things that were different between the logs on the PQ and the HTML page itself. I should've written UI instead of GUI, as a good developer is also a good UI designer. The consistency of the order which logs come up on PQ and HTML is in fact UI - User Interface. One is graphical the other not. My point is that it's not consistent and you both know that writing consistent, standard-abiding and easy-to-navigate programs is what the end-user experience is all about!