On 18/10/12 08:18, David Anderson wrote:
> OK, I think I fixed this; please try it on SETI@home.
> -- David

Indeed fixed.

Works very well thanks.

Regards,
Martin


> On 17-Oct-2012 5:38 PM, Martin wrote:
>> On 17/10/12 22:56, David Anderson wrote:
>>> Martin:
>>> Do you have "Jump to first new post in thread automatically"
>>> checked in your community preferences?
>>> -- David
>>
>> Yes, and that part works fine for an unread thread: The first unread
>> post is correctly positioned. All good.
>>
>> However:
>>
>>
>> This point is for when long threads have already been visited and so all
>> posts have been marked as having been read. To *revisit* the thread, you
>> are dumped at the very start. Hence, to see the most recent post
>> requires multiple clicks and loads to select the last page and then
>> "page end" or scroll to see the last post to then be able to quote/reply
>> or thread post a reply.
>>
>> Hence, for user convenience for a thread with no unread posts (all posts
>> already read), always position the user for that case on the last page
>> of the thread for easy access to the most recent (read) post.
>>
>> The most often use case is you do that to continue an old thread.
>>
>>
>> In contrast, to see the very first ever post in a thread (as is the
>> default at present) is rarely wanted.
>>
>> (I have "Posts: Oldest first" set for chronological order top-down reading.)
>>
>> Thanks,
>> Martin
>>
>>
>>> On 17-Oct-2012 6:48 AM, Martin wrote:
>>>> On 12/10/12 14:06, Martin wrote:
>>>>
>>>>> Fix the placing for "already read threads" to always position to the
>>>>> most recent post?
>>>>>
>>>>> #3 fix thread placing for already read threads
>>>>
>>>> Less often an annoyance but still one to be fixed, please?
>>>>
>>>> (Briefly: Always jump first to the last page/post for an already read
>>>> thread.)
>>>>
>>>>
>>>> Regards,
>>>> Martin
>>>>
>>>>
>>>>
>>>>> The normal usage is to add a post some time later to a thread that has
>>>>> already been read. At present, with "oldest post first" you are taken to
>>>>> the very start of the thread which then requires multiple clicks through
>>>>> the paging to get to the end of the thread to add a post... All rather
>>>>> cumbersome and time consuming, especially on mobile devices!...
>>>>>
>>>>>
>>>>> All this really comes to the semantics of "oldest post first".
>>>>>
>>>>> I use and translate the "sort" setting "oldest post first" as actually
>>>>> meaning "chronological order" or "top -> down posting order". Note: NOT
>>>>> as described on the forum settings and NOT as programmed...
>>>>>
>>>>> In the strict sense, "oldest post first" isn't that useful for normal
>>>>> forum use/interaction. However, "top -> down" or "bottom -> up" posting
>>>>> is more descriptive phrase but that also can be misinterpreted...
>>>>>
>>>>>
>>>>> Regardless of descriptions and semantics... Always position to either
>>>>> the latest post or the first unread post please?
>>>>>
>>>>>
>>>>> Regards,
>>>>> Martin



-- 
--------------------
Martin Lomas
m_boincdev ml1 co uk.ddSPAM.dd
--------------------
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to