newsbin.com

Version 6.52B3 -

1. Hide Old Not working in Internet Search.

For example:
Search for .mp3.
List appears (currently 1,270).
Delete all except ones in audiobook groups (leaves about 120)
Select Hide Old and nothing changes, all 1,270 still appear.

Clear the search so that nothing is showing.
Do 2nd search for .mp3 and get a list that contains both deleted and non-deleted records (the same 1,270 records).
Select Hide Old and nothing changes, both still appear.
Select Hide Old a second time and the deleted records disappear and only the non-deleted records show.


2. Not searching for older unread records.

If I do a search with just an * I get 3,229 records that all have Dates for 0d:00h:00m.

If I delete all of those and do a 2nd search with * I'd expect to get an older set of records that I haven't seen. Instead the same 3,229 records even though I've already marked them as hidden and even though Hide Old is turned on.

I know there are other records out there that I haven't read that are older than those same 3,229 records.

Shouldn't searches return records that haven't been read and ignore one's that have been read during a search even if there is a limit to the number of records that are returned?

i.e., If there are 10,000 unread records, and I read them sequentially, and there is a limit of 3200 records returned during a search I'd expect to see records 1 through 3,200 on my first search. If I mark those records as read and do a second search I would expect to see records 3,201 - 6,400 and then 6,401 - 9,600.

Instead I keep seeing 1 - 3,200 and even those are not being hidden when Hide Old is selected.

Thanks - Bill

I'm looking at hide old for the next beta. Search works completely differently than header downloads so, the "old" tracking has to work completely differently too.

If I delete all of those and do a 2nd search with * I'd expect to get an older set of records that I haven't seen. Instead the same 3,229 records even though I've already marked them as hidden and even though Hide Old is turned on

That's not how it works. You have to hit the arrow that points to the left to pull older records when using wild card and search. The search server has no idea if you deleted something or not. If you keep hitting the back Arrow, you'll walk backwards through the groups one day at a time.

Just to make sure I'm not causing confusion about what I'm asking about I use the subscription based Search tab inside Newsbin Pro 99% of the time because I got tired of wait times when downloading headers from large groups. Search is much easier to use to get to files I'm looking for.

So, when you say

If you keep hitting the back Arrow, you'll walk backwards through the groups one day at a time.

I'm not clear on how that would get me additional records from UseNet that are older than the ones that I've already retrieved? I'm not really even clear on what back arrow you're referring to.

I understand the search server would not know if I deleted something but Newsbin Pro (located on my computer) does keep track since it would have to in order to be able to tell which records to "Hide" when "Hide Old" is selected.

Also, when I say deleted I'm only using that word because that is the hotkey Newsbin Pro uses to "Mark Posts Old".

Thanks for the help.

It's the 5th button in on in the search tab.

Think so it this way.

1 - The first time you search using wild card, you get the last 24 hours worth of posts.

2 - When you click the back arrrow, Newsbin tells the server "send me the next days's worth".

You're never going to be able to "wildcard" through 200 days of headers. I mean you can but, you won't want to. That's not really what wild card was designed for.

I'm not saying you won't be able to do this in the future. Dex and I are considering it in the search re-design but, you can't do it now. Search was really designed for you to do searching not for pulling a full header list. It COULD do the header list and I'm working towards it but, it's not there now. It'll require me to store and note the search results so, they act more like headers.