Why is This Happening?

I click on "New Posts" to see what is new, I then see that a thread I am "Following" shows a post I have not read.
I then click on "(nothing new) go to first unseen of 1" to see what I have not read only to find that yes I have seen the last post.

IMAGE LINK: https://flic.kr/p/22UA​zfC

IMAGE LINK: https://flic.kr/p/22UA​zhb

IMAGE LINK: https://flic.kr/p/21SE​KaG

Hi Charles. When you are in the thread click on "Followed" in the upper right corner, then click "Mark all posts seen". This will fix the problem.

Thank you..... never had to do that before...

Inspeqtor wrote in post #18527807
I click on "New Posts" to see what is new, I then see that a thread I am "Following" shows a post I have not read.
I then click on "(nothing new) go to first unseen of 1" to see what I have not read only to find that yes I have seen the last post.

IMAGE LINK: https://flic.kr/p/22UA​zfC Santa3A by inspeqtor, on Flickr

IMAGE LINK: https://flic.kr/p/22UA​zhb Santa2A by inspeqtor, on Flickr

I then go back and click on "New Posts" only to see this yet again.

IMAGE LINK: https://flic.kr/p/21SE​KaG Santa1A by inspeqtor, on Flickr

Why does it say (nothing new) but also says and does not clear "go to first unseen 1"?

Normally when I see this, after I then click on that the next time I click on "New Posts" that statement has cleared itself.

This only seems to happen to me if I haven't paused for a few milliseconds at the bottom of the page. If I wait just a little longer before hitting the back button my mouse, everything is fine.

Phoenixkh wrote in post #18528140
This only seems to happen to me if I haven't paused for a few milliseconds at the bottom of the page. If I wait just a little longer before hitting the back button my mouse, everything is fine.

Thank you, but... I did pause a few seconds, and I did this 3-4 times!

Why is This Happening?

You mean why did my aunt give me a subscription to Shutterbug?

rrblint wrote in post #18527934
Hi Charles. When you are in the thread click on "Followed" in the upper right corner, then click "Mark all posts seen". This will fix the problem.

But the problem is that the software is supposed to know what we have seen and what we haven't, and it is supposed to report this information accurately. . So if we have to do it manually, such as you suggest, that shows that something in the software is not functioning properly.

Rather than just make the inaccurate notice go away, I would like to understand the problem - what is it in the code that is causing the problem? . What lines of code need to be re-written? . I am kind of like Charles; I want to know why it is happening.

.

Tom Reichner wrote in post #18528529
I would like to understand the problem - what is it in the code that is causing the problem? . What lines of code need to be re-written? . I am kind of like Charles; I want to know why it is happening.

Really?

It's all in the javascript code AMASS_membertools.min.​js, feel free to examine it (all javascript code is there in html source). You can beautify the minified code in order to make it legible. You can debug the boundaries if you set var debugboundaries = true in dev console after the code has initilized and you can recalc to see them visually by e.g. changing a page width.

The base reason for the problem is that pixel based seen boundary calculation AMASS_get_seentargets(​) for the last post in page sometimes fails to store a proper position for AMASS_check_seentarget​s(), this is related to slow load of page elements and some other issues. This is fixed in 2.0. If you want to see what was the fix (lots of lines in various scripts and functions), when 2.0 is out, you can "diff" all the javascript to view changes.

Tom Reichner wrote in post #18528529
But the problem is that the software is supposed to know what we have seen and what we haven't, and it is supposed to report this information accurately. . So if we have to do it manually, such as you suggest, that shows that something in the software is not functioning properly.

Rather than just make the inaccurate notice go away, I would like to understand the problem - what is it in the code that is causing the problem? . What lines of code need to be re-written? . I am kind of like Charles; I want to know why it is happening.

.

Tom I agree. My post was meant to help Charles and others to alleviate the problem. As Pekka says, it is fixed in AMASS! 2.0.

Tom Reichner wrote in post #18528529
But the problem is that the software is supposed to know what we have seen and what we haven't, and it is supposed to report this information accurately. . So if we have to do it manually, such as you suggest, that shows that something in the software is not functioning properly.

Rather than just make the inaccurate notice go away, I would like to understand the problem - what is it in the code that is causing the problem? . What lines of code need to be re-written? . I am kind of like Charles; I want to know why it is happening.

.

You said it better than I did Tom! I could not understand why it did not clear itself after going thru the steps I went thru multiple times.

Glad to hear it is fixed in 2.0!

Pekka wrote in post #18528558
The base reason for the problem is that pixel based seen boundary calculation AMASS_get_seentargets(​) for the last post in page sometimes fails to store a proper position for AMASS_check_seentarget​s(), this is related to slow load of page elements and some other issues. This is fixed in 2.0. If you want to see what was the fix (lots of lines in various scripts and functions), when 2.0 is out, you can "diff" all the javascript to view changes.

This is helpful, Pekka!

I wouldn't understand the code itself, but your explanation gives me the level of understanding that I was looking for.

Slow page loads ....... that seems to make sense to me, how things could get glitchy if a page doesn't load properly. . It makes sense because I have seen the same type of thing happen elsewhere - on many other websites, when pages take forever to load, there are often glitchy things on the page once it does finally load (or sometimes it never loads completely unless I refresh).

.

Here's what the first of eight screens of AMASS_membertools.min.​js looks like.

AZGeorge wrote in post #18530289
Here's what the first of eight screens of AMASS_membertools.min.​js looks like.

That is all Greek to me!