Conversation
CSharpMath.Forms.Example/CSharpMath.Forms.Example.UWP/CSharpMath.Forms.Example.UWP.csproj
Outdated
Show resolved
Hide resolved
|
Maybe we should remove panning/dragging. It is from a time when view sizes were buggy and views are required to fill the entire available size. Panning/dragging is also buggy on Avalonia (the hit detection requires you to click a non-transparent pixel requiring precise cursor movement, and you can drag out of view bounds). Now that view sizes is getting fixed (#32, #136), we should replace all uses of panning/dragging with ScrollViews. If we are to remove panning/dragging anyways, we might as well ignore this issue for now. |
What about line breaks then ? (or I didn't get the point how it will be implemented) |
|
Panning/dragging is independent of line breaking. People can already use TextView in ScrollView as seen in #136. |


This should finish #123, #136, #137 and possibly #138.