You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we approach the release of v2, this document will continue to evolve. Our ultimate objective is to ensure that v2 functions identically to v1 in every aspect. However, it is important to note that in certain specific areas, achieving a 100% match may present inherent challenges.
Main Change "Performance" WinForms -> WPF
Moving from WinForms to WPF for our open-source tool simplifies UI changes and aligns with our goal of achieving cross-platform compatibility, all while enhancing overall performance.
=>WinForms overhead around ~0,7s for 3000i tems, we will make benchmarks at the end
=> maybe show here difference of fading with video/gif
Settings menu WinForms -> WPF
=> we will make screenshots at the end
WPF has other font rendering engine than v1 or Windows Explorer
The font may not appear 100% identical in WPF due to inherent differences in rendering engines:
windows explorer (win10)
v1
WPF
Switched context menu location and behavior as it is done by Windows Explorer
The behavior of where the context menu appears has been adjusted to closely resemble how Windows Explorer does it. bfd50ae
In v1 when context menu open and you press again right click this will only close the context menu. In v2 right click always opens context menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As we approach the release of v2, this document will continue to evolve. Our ultimate objective is to ensure that v2 functions identically to v1 in every aspect. However, it is important to note that in certain specific areas, achieving a 100% match may present inherent challenges.
Main Change "Performance" WinForms -> WPF
Moving from WinForms to WPF for our open-source tool simplifies UI changes and aligns with our goal of achieving cross-platform compatibility, all while enhancing overall performance.
=>WinForms overhead around ~0,7s for 3000i tems, we will make benchmarks at the end
=> maybe show here difference of fading with video/gif
Settings menu WinForms -> WPF
=> we will make screenshots at the end
WPF has other font rendering engine than v1 or Windows Explorer
The font may not appear 100% identical in WPF due to inherent differences in rendering engines:
Switched context menu location and behavior as it is done by Windows Explorer
bfd50ae
Beta Was this translation helpful? Give feedback.
All reactions