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
Problem:
The table views (e.g. security log, firewall rules and connections) do not look and feel or can be handled like normal Windows tables.
This gets really annoying when the window gets resized (e.g. maximized / restored) which also resets all user defined column widths, resulting in completely unusable tables like this one:
I did not even have to anonymise anything here since you cannot see something important. (The same can happen with the other tables, like the security log.)
Expected behaviour:
The tables should be usable like any other table on Windows. A column width handle should only change the width of one column. There is no use in hiding even more data in all other columns when I try to get data visible of one column.
There is already a visible horizontal scrollbar when the table gets "too wide" due to some of these bugs, so, most likely there will be no problem with visibility when allowing normal table handling through user interactions.
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for your feedback (well... your feedbacks, plural 😉).
As you probably guessed, WFN shouldn't look that ugly / buggy (well, not that much, it's still a beta afterall). I wasn't able to test on Win7 but that comes as a surprise since WFN doesn't use any Win10 specific things (Window theming is fully custom). Some issues you mentioned are probably linked to a single issue (missing styles compared to the Win10 version?).
Will check that when I get some time (no ETA... as usual).
Problem:
The table views (e.g. security log, firewall rules and connections) do not look and feel or can be handled like normal Windows tables.
This gets really annoying when the window gets resized (e.g. maximized / restored) which also resets all user defined column widths, resulting in completely unusable tables like this one:
I did not even have to anonymise anything here since you cannot see something important. (The same can happen with the other tables, like the security log.)
Expected behaviour:
The tables should be usable like any other table on Windows. A column width handle should only change the width of one column. There is no use in hiding even more data in all other columns when I try to get data visible of one column.
There is already a visible horizontal scrollbar when the table gets "too wide" due to some of these bugs, so, most likely there will be no problem with visibility when allowing normal table handling through user interactions.
The text was updated successfully, but these errors were encountered: