TabSRMM: if you scrolled up the chat log and new msg arives - don't autoscroll to the bottom

[GoogleCodeExporter]

I've requested this feature for TabSRMM, and some hostile developer replied 
that he won't add this feature since it would work only for default view, and 
if would work in IEView and H++ then he might add this feature to TabSRMM.
Please, add this feature for History++.

https://code.google.com/p/miranda/issues/detail?id=1230

Original issue reported on code.google.com by iDru...@gmail.com on 10 Jan 2011 at 10:06

[GoogleCodeExporter]

tabSRMM has F12 to disable autoscroll

Original comment by themiron.ru on 10 Oct 2011 at 5:05

• Changed state: Invalid

[GoogleCodeExporter]

That's the point of my suggestion - to not make people click a button 
themselves.
If you do scroll your chat log - you definitely don't need to get interrupted 
by an instant scroll-down caused by a new arrived message.
That's an awesome feature, and it's awesomeness is in it's automatism, when you 
don't need to manually click any buttons.
And when you manually scroll back to the bottom of the chat log - everything 
should be brought back to the normal behavior.

How I want to be mistaken in my thoughts, but I think you won't listen to any 
suggestions with arguments, no matter how useful they are.
If it took you 9 months to just write these 33 letters - I can only guess, how 
long would it take you to write any code... right?

Original comment by iDru...@gmail.com on 10 Oct 2011 at 10:42

[GoogleCodeExporter]

Thanks for the suggestions, patches are welcome

Original comment by themiron.ru on 10 Oct 2011 at 6:14

[GoogleCodeExporter]

Who would attempt to write a patch for an issue with Status: Invalid?

Original comment by iDru...@gmail.com on 10 Oct 2011 at 6:17

[GoogleCodeExporter]

Invalid status is here because h++ just exports grid control for tabsrmm and 
some kind of API. Running, tabsrmm makes h++ grid scroll the the bottom, same 
behaviour as for ieview. F12 is the hotkey to stop scrolling of tabsrmm, not of 
h++.
Of course, h++ could prevent itself from beeing scrolled (like in pseudo-edit 
mode), and that's why patches are welcome.
Is it clear now?

Original comment by themiron.ru on 10 Oct 2011 at 6:28

[GoogleCodeExporter]

Have you read this?

> I've requested this feature for TabSRMM, and some hostile developer replied 
that
> he won't add this feature since it would work only for default view, and if
> would work in IEView and H++ then he might add this feature to TabSRMM.

Original comment by iDru...@gmail.com on 10 Oct 2011 at 6:32

[GoogleCodeExporter]

Have you read this?

> tabSRMM has F12 to disable autoscroll
> Thanks for the suggestions, patches are welcome
> Status: Invalid

Original comment by themiron.ru on 10 Oct 2011 at 6:35

[GoogleCodeExporter]

Yes and this makes no sense, as
> Status: Invalid
means that the suggestion was rejected, then why do you write 
> patches are welcome
?

> tabSRMM has F12 to disable autoscroll
This commentary also makes no sense, as we are both aware of that function and 
the initial intention of opening this issue was to improve that function in the 
suggested way.

Our dialogue is like:
- sir, you know that this is red, and that it actually should be green?
- yes, but you can use green glasses to see it green.
- but why not just paint it green?
- thanks for your suggestion, but you may wear green glasses if you would like 
to see it green.

Original comment by iDru...@gmail.com on 10 Oct 2011 at 6:53

[GoogleCodeExporter]

First, nobody wants this improvement besides you.
Second, pointless arguing isn't the best way to force developer to make the 
changes.
Third, log freezing is not up to log control what definitely will confuse 
existing users.
If you can't find the way to describe the explicit importance and need of the 
feature even for you but you really need it, okie. It's opensource - just make 
a patch, send it to me and probably I will review it. If you have no ability to 
make it, not a problem, go buy someone's skills to do it for you and send me a 
patch. If not, there's no point to be rude, just stop using the plugin and 
don't keep wasting my time.
I have no plan to implement standalone log freezing.

Original comment by themiron.ru on 10 Oct 2011 at 7:46

• Changed state: WontFix

[GoogleCodeExporter]

Yes, you are right. Arguing with you is just a waste of time.

Original comment by iDru...@gmail.com on 10 Oct 2011 at 8:07