Can I disable this: OE scrolls down NG list auto'ly

"Bruce Hagen" <Nospam.DeleteThis@mymail.invalid> wrote:
> The top of the display in your case will always show the most recently
> started thread.

No, it will not. If I use ctrl+A and ctrl+Q to mark all threads as "read",
then press F5 to download any new postings, if the only new activity (let's
say) is a thread that would normally not fit on the display (I get about 35
with the Preview Pane disabled), the display is scrolled down to include
that thread.

As I recall, that thread with new activity is at the bottom of the display.
If not the bottom, then "near" the bottom. Unfortunately, I cannot cause
the situation to happen; I have to wait for it. As I said, it is very
infrequent; and that's why it is an annoyance.


> It will not change to the most recently posted to thread.
> OE doesn't let you have your cake and eat it too.

I think you misunderstood. I am not trying to see the most-recently posted
thread. Just the opposite. I am trying to coerce OE __not__ to show me the
most-recently posted thread necessarily. Instead, I want the behavior that
you presumed incorrectly, namely: I want OE to always show the
most-recently started thread at the top of the display.


> You can Watch or Flag certain threads and manually change
> the sort order as you do with Show All Messages, but there
> is nothing that will change the sort order on its own.

I am not interested in changing the order. Nor am I interested in putting a
Watch or Flag on any particular thread.

I simply want the top of the display to always be the top of the list, i.e.
the most-recently posted thread (since I set to sort by Sent in descending
order), regardless of what thread might have had the most recently activity.

This is a problem only when the first 35 threads (in my case) have no recent
activity, and the most-recent activity occurs in the 36th thread or earlier.
OE scrolls down the display to include that active thread (36th or earlier),
causing the 1st thread or more to scroll up off the display.

Moreover, I want "Group by Conversation". I do not want to disable that
grouping, set Watches or Flags, then re-enable "Group by Conversation".
Again, that is the antithesis of what I want. I am not interested in the
latest activity per se. I am simply interested in a consistent, predictable
display of the threads, specifically: the top of the display is the
most-recently started thread.

That is not how OE behaves, at least not revision 6.00.2900.5512
(xpsp.080413-2105).

I would not be posting this inquiry if OE behaved as you presume.


----- original message -----

"Bruce Hagen" <Nospam.DeleteThis@mymail.invalid> wrote in message
news:%23NajP$SJKHA.4608@TK2MSFTNGP02.phx.gbl...
> WYSIWYG. The top of the display in your case will always show the most
> recently started thread. It will not change to the most recently posted to
> thread. OE doesn't let you have your cake and eat it too. You can Watch or
> Flag certain threads and manually change the sort order as you do with
> Show All Messages, but there is nothing that will change the sort order on
> its own.
> --
>
> Bruce Hagen
> MS-MVP [Mail]
> Imperial Beach, CA
>
>
> "WhatsUp31415" <whatsup31415.DeleteThis@live.com> wrote in message
> news:e7lS53SJKHA.4376@TK2MSFTNGP03.phx.gbl...
>> How can I disable the following OE feature?
>>
>> For my News account, typically I set the option "Group By Conversation",
>> and
>> I order the list by Sent in descending order. My intent is: when I
>> click
>> on a NG, I want to see the most recently posted threads at the top of the
>> display (albeit not necessarily the threads with the most recent
>> responses).
>>
>> However, if the first thread with an unread response would not normally
>> appear on the display, the list is scrolled down to include that thread.
>> Consquently, the top of the display is not always the most recently
>> posted
>> threads.
>>
>> This causes some confusion, especially because it is relatively unusual
>> in
>> the very active NGs that I monitor. So I sometimes forget to look at the
>> scroll bar to ensure that I am indeed looking at the top of the list.
>>
>> How can I disable this feature of changing the focus of the list
>> (scrolling
>> down automagically)?
>>
>> I do not want to prune the NG because I may be interested in the earlier
>> threads. For example, I will use ctrl+h to toggle between the full list
>> and
>> "Show Replies to My Messages".
>>
>

PS....

I wrote:
> If I use ctrl+A and ctrl+Q to mark all threads as "read", then press F5 to
> download any new postings, if the only new activity
> (let's say) is a thread that would normally not fit on the display
> (I get about 35 with the Preview Pane disabled), the display is
> scrolled down to include that thread.

Apparently, this undesirable behavior is not quite as consistent as I
thought.

I just did ctrl+A and ctrl+Q of a NG, went to another NG, then returned to
the first NG. (And actually, that is what I have been doing, not pressing
F5.) The top of the display showed the most-recently started thread, but
when I scroll down, I found a thread that had a response in the interim.

That is exactly the behavior that I want -- and the behavior that Bruce says
I should expect.

I 'spose I can experiment with this scenario by posting bogus responses to
old threads and hoping there is no activity in more-recent threads.
Probably easier to do in the wee hours when there is typically much less
activity in the NGs that I monitor.

In any case, I infer from Bruce's insistance that there is no option that
controls this behavior. So I am SOL when it happens .

I will post an update if I can find a repeated scenario that demonstrates
the undesired (mis)behavior.


----- original message -----

"WhatsUp31415" <whatsup31415.RemoveThis@live.com> wrote in message
news:uwzNGkTJKHA.356@TK2MSFTNGP05.phx.gbl...
> "Bruce Hagen" <Nospam.RemoveThis@mymail.invalid> wrote:
>> The top of the display in your case will always show the most recently
>> started thread.
>
> No, it will not. If I use ctrl+A and ctrl+Q to mark all threads as
> "read", then press F5 to download any new postings, if the only new
> activity (let's say) is a thread that would normally not fit on the
> display (I get about 35 with the Preview Pane disabled), the display is
> scrolled down to include that thread.
>
> As I recall, that thread with new activity is at the bottom of the
> display. If not the bottom, then "near" the bottom. Unfortunately, I
> cannot cause the situation to happen; I have to wait for it. As I said,
> it is very infrequent; and that's why it is an annoyance.
>
>
>> It will not change to the most recently posted to thread.
>> OE doesn't let you have your cake and eat it too.
>
> I think you misunderstood. I am not trying to see the most-recently
> posted thread. Just the opposite. I am trying to coerce OE __not__ to
> show me the most-recently posted thread necessarily. Instead, I want the
> behavior that you presumed incorrectly, namely: I want OE to always show
> the most-recently started thread at the top of the display.
>
>
>> You can Watch or Flag certain threads and manually change
>> the sort order as you do with Show All Messages, but there
>> is nothing that will change the sort order on its own.
>
> I am not interested in changing the order. Nor am I interested in putting
> a Watch or Flag on any particular thread.
>
> I simply want the top of the display to always be the top of the list,
> i.e. the most-recently posted thread (since I set to sort by Sent in
> descending order), regardless of what thread might have had the most
> recently activity.
>
> This is a problem only when the first 35 threads (in my case) have no
> recent activity, and the most-recent activity occurs in the 36th thread or
> earlier. OE scrolls down the display to include that active thread (36th
> or earlier), causing the 1st thread or more to scroll up off the display.
>
> Moreover, I want "Group by Conversation". I do not want to disable that
> grouping, set Watches or Flags, then re-enable "Group by Conversation".
> Again, that is the antithesis of what I want. I am not interested in the
> latest activity per se. I am simply interested in a consistent,
> predictable display of the threads, specifically: the top of the display
> is the most-recently started thread.
>
> That is not how OE behaves, at least not revision 6.00.2900.5512
> (xpsp.080413-2105).
>
> I would not be posting this inquiry if OE behaved as you presume.
>
>
> ----- original message -----
>
> "Bruce Hagen" <Nospam.RemoveThis@mymail.invalid> wrote in message
> news:%23NajP$SJKHA.4608@TK2MSFTNGP02.phx.gbl...
>> WYSIWYG. The top of the display in your case will always show the most
>> recently started thread. It will not change to the most recently posted
>> to thread. OE doesn't let you have your cake and eat it too. You can
>> Watch or Flag certain threads and manually change the sort order as you
>> do with Show All Messages, but there is nothing that will change the sort
>> order on its own.
>> --
>>
>> Bruce Hagen
>> MS-MVP [Mail]
>> Imperial Beach, CA
>>
>>
>> "WhatsUp31415" <whatsup31415.RemoveThis@live.com> wrote in message
>> news:e7lS53SJKHA.4376@TK2MSFTNGP03.phx.gbl...
>>> How can I disable the following OE feature?
>>>
>>> For my News account, typically I set the option "Group By Conversation",
>>> and
>>> I order the list by Sent in descending order. My intent is: when I
>>> click
>>> on a NG, I want to see the most recently posted threads at the top of
>>> the
>>> display (albeit not necessarily the threads with the most recent
>>> responses).
>>>
>>> However, if the first thread with an unread response would not normally
>>> appear on the display, the list is scrolled down to include that thread.
>>> Consquently, the top of the display is not always the most recently
>>> posted
>>> threads.
>>>
>>> This causes some confusion, especially because it is relatively unusual
>>> in
>>> the very active NGs that I monitor. So I sometimes forget to look at
>>> the
>>> scroll bar to ensure that I am indeed looking at the top of the list.
>>>
>>> How can I disable this feature of changing the focus of the list
>>> (scrolling
>>> down automagically)?
>>>
>>> I do not want to prune the NG because I may be interested in the earlier
>>> threads. For example, I will use ctrl+h to toggle between the full list
>>> and
>>> "Show Replies to My Messages".
>>>
>>
>

[Repost. Hmm, this response never seemed to appear on the server, even an
hour later. Anyway, I have an update.]

I wrote:
> I will post an update if I can find a repeated scenario
> that demonstrates the undesired (mis)behavior.

Well, this just happened in microsoft.public.excel.newusers.

And I might have found a way to duplicate the misbehavior; at least, it
worked once.

In a NG with multiple pages (screens) of threads (remember: "Group by
Conversation" is set), first press ctrl+A and ctrl+Q to mark all threads as
"read". Then mark a thread on the 2nd page as "unread". (I chose a thread
with no responses. [*]) Exit the NG (go to another NG), then re-enter the
NG.
Repeat those steps as needed if there was any recent activity in threads on
the first page.

Otherwise, in my case, the display was scrolled down so that the "unread"
thread is just above the bottom of the display (2nd from the bottom),
causing the top of the list to be scrolled off the top. In other words, the
scroll bar is not at the top.

[*] Update.... It is not necessary to choose a thread with no responses.
Of course, the original observation involved threads with responses. And
the above procedure works by marking a response as "unread" as well.


----- original message -----

"WhatsUp31415" <whatsup31415 RemoveThis @live.com> wrote in message
news:OuZZaOUJKHA.356@TK2MSFTNGP05.phx.gbl...
> [I posted this once. It appeared on the server once. When I re-entered
> the NG later, I got an error "no longer on the server". The item in my NG
> listing was lined through; and eventually it was removed from my cache.
> Why; how was it removed from the server? The server should not recognize
> a "cancel" message unless it is from the sender.]
>
> PS....
>
> I wrote:
>> If I use ctrl+A and ctrl+Q to mark all threads as "read", then press F5
>> to download any new postings, if the only new activity
>> (let's say) is a thread that would normally not fit on the display
>> (I get about 35 with the Preview Pane disabled), the display is
>> scrolled down to include that thread.
>
> Apparently, this undesirable behavior is not quite as consistent as I
> thought.
>
> I just did ctrl+A and ctrl+Q of a NG, went to another NG, then returned to
> the first NG. (And actually, that is what I have been doing, not pressing
> F5.) The top of the display showed the most-recently started thread, but
> when I scroll down, I found a thread that had a response in the interim.
>
> That is exactly the behavior that I want -- and the behavior that Bruce
> says
> I should expect.
>
> I 'spose I can experiment with this scenario by posting bogus responses to
> old threads and hoping there is no activity in more-recent threads.
> Probably easier to do in the wee hours when there is typically much less
> activity in the NGs that I monitor.
>
> In any case, I infer from Bruce's insistance that there is no option that
> controls this behavior. So I am SOL when it happens .
>
> I will post an update if I can find a repeated scenario that demonstrates
> the undesired (mis)behavior.
>
>
> ----- original message -----
>
> "WhatsUp31415" <whatsup31415 RemoveThis @live.com> wrote in message
> news:uwzNGkTJKHA.356@TK2MSFTNGP05.phx.gbl...
>> "Bruce Hagen" <Nospam RemoveThis @mymail.invalid> wrote:
>>> The top of the display in your case will always show the most recently
>>> started thread.
>>
>> No, it will not. If I use ctrl+A and ctrl+Q to mark all threads as
>> "read", then press F5 to download any new postings, if the only new
>> activity (let's say) is a thread that would normally not fit on the
>> display (I get about 35 with the Preview Pane disabled), the display is
>> scrolled down to include that thread.
>>
>> As I recall, that thread with new activity is at the bottom of the
>> display. If not the bottom, then "near" the bottom. Unfortunately, I
>> cannot cause the situation to happen; I have to wait for it. As I said,
>> it is very infrequent; and that's why it is an annoyance.
>>
>>
>>> It will not change to the most recently posted to thread.
>>> OE doesn't let you have your cake and eat it too.
>>
>> I think you misunderstood. I am not trying to see the most-recently
>> posted thread. Just the opposite. I am trying to coerce OE __not__ to
>> show me the most-recently posted thread necessarily. Instead, I want the
>> behavior that you presumed incorrectly, namely: I want OE to always show
>> the most-recently started thread at the top of the display.
>>
>>
>>> You can Watch or Flag certain threads and manually change
>>> the sort order as you do with Show All Messages, but there
>>> is nothing that will change the sort order on its own.
>>
>> I am not interested in changing the order. Nor am I interested in
>> putting a Watch or Flag on any particular thread.
>>
>> I simply want the top of the display to always be the top of the list,
>> i.e. the most-recently posted thread (since I set to sort by Sent in
>> descending order), regardless of what thread might have had the most
>> recently activity.
>>
>> This is a problem only when the first 35 threads (in my case) have no
>> recent activity, and the most-recent activity occurs in the 36th thread
>> or earlier. OE scrolls down the display to include that active thread
>> (36th or earlier), causing the 1st thread or more to scroll up off the
>> display.
>>
>> Moreover, I want "Group by Conversation". I do not want to disable that
>> grouping, set Watches or Flags, then re-enable "Group by Conversation".
>> Again, that is the antithesis of what I want. I am not interested in the
>> latest activity per se. I am simply interested in a consistent,
>> predictable display of the threads, specifically: the top of the display
>> is the most-recently started thread.
>>
>> That is not how OE behaves, at least not revision 6.00.2900.5512
>> (xpsp.080413-2105).
>>
>> I would not be posting this inquiry if OE behaved as you presume.
>>
>>
>> ----- original message -----
>>
>> "Bruce Hagen" <Nospam RemoveThis @mymail.invalid> wrote in message
>> news:%23NajP$SJKHA.4608@TK2MSFTNGP02.phx.gbl...
>>> WYSIWYG. The top of the display in your case will always show the most
>>> recently started thread. It will not change to the most recently posted
>>> to thread. OE doesn't let you have your cake and eat it too. You can
>>> Watch or Flag certain threads and manually change the sort order as you
>>> do with Show All Messages, but there is nothing that will change the
>>> sort order on its own.
>>> --
>>>
>>> Bruce Hagen
>>> MS-MVP [Mail]
>>> Imperial Beach, CA
>>>
>>>
>>> "WhatsUp31415" <whatsup31415 RemoveThis @live.com> wrote in message
>>> news:e7lS53SJKHA.4376@TK2MSFTNGP03.phx.gbl...
>>>> How can I disable the following OE feature?
>>>>
>>>> For my News account, typically I set the option "Group By
>>>> Conversation", and
>>>> I order the list by Sent in descending order. My intent is: when I
>>>> click
>>>> on a NG, I want to see the most recently posted threads at the top of
>>>> the
>>>> display (albeit not necessarily the threads with the most recent
>>>> responses).
>>>>
>>>> However, if the first thread with an unread response would not normally
>>>> appear on the display, the list is scrolled down to include that
>>>> thread.
>>>> Consquently, the top of the display is not always the most recently
>>>> posted
>>>> threads.
>>>>
>>>> This causes some confusion, especially because it is relatively unusual
>>>> in
>>>> the very active NGs that I monitor. So I sometimes forget to look at
>>>> the
>>>> scroll bar to ensure that I am indeed looking at the top of the list.
>>>>
>>>> How can I disable this feature of changing the focus of the list
>>>> (scrolling
>>>> down automagically)?
>>>>
>>>> I do not want to prune the NG because I may be interested in the
>>>> earlier
>>>> threads. For example, I will use ctrl+h to toggle between the full
>>>> list and
>>>> "Show Replies to My Messages".
>