Open kevwkev opened 5 months ago
Hi! Thank you for reporting this. It seems that this is the problem made by the control ScollViewerEx.cs. I'll check that later cuz I'm in the weeds right now. 😕
Help needed! I can't solve this after a few attempts.
这段注释掉就正常了,但是不知道有无副作用
有点难评但是管用
个人感觉是ScrollInfoAdapter.SetVerticalOffset(double offset)
执行动效的时候寄了
把 ScrollViewerEx 改成 ScrollViewer 的方案是不可取的。ScrollViewerEx 存在的意义就是修复和优化 WPF 自带的垃圾滚动逻辑。我们解决这个问题只能从 ScrollViewer 本身下手。
I don't know how far your testing did go, I just realized both functions ScrollToHome
and ScrollToEnd
do work a single time after the application is started. Then I found out they work again after the contrary function is called, meaning a not working ScrollToEnd
function does work again after ScrollToHome
is called once.
In conclusion there is at least a workaround for now, just call ScrollToHome
everytime before you call ScrollToEnd
. It works in my test project, within a slower program or an a slower machine, adding texts fast, I would imaging this approach to be problemtic though.
The ScrollToEnd() function appears ineffective with TextBox, tested in both code-behind and MVVM utilizing a behavior extension of the TextBox control.
===code-hehind===
===behavior extension for MVVM====