A lot of the replies in this thread show why an Option to sw between word wrap or not , is needed! (some prefer it, others do not), especially when the status quo has been changed.
That screenshot is 1281px wide, adding the missing menu from winbox probably results to 1366. That again, ain't 1080p, because if it was it should've been close to 1920 not to 1366.
Disable the Display Scaling.
And you can always export the log and view it with your favourite text editor, wrapped or not.
Thanks for reply-
This was an example image i made, so please ignore the actual pixel width of the image. I think you did get the point of what i was trying to show w the image. (also i dont use display scaling, i actually hate it, im always at 100%)
Yes ofcourse i can print/export the log and view it wrapped in winbox terminal or file=out.txt then open it, or i could view it in our splunk instances.
However all of those options take a bit longer than just viewing it in winbox-> log, as was the case before (ie a feature that used to exist in winbox, but now does not (word wrapped log window))
also i mainly spoke in the context of in the field where it would be nice to only need winbox, and not external tools (and scrolling/finding a single log message in winbox-> terminal, among a /log print of 1000+ messages can be difficult).
I would suggest that you can double-click on a log event so the full content is displayed in a properties box.
Excellent! i cant believe i hadnt tried that (as i use that same action in other winbox lists/output all the time, like connections list of FW tab)-> ~15 yrs of using winbox and still finding new features! Although this does not fully solve the problem, as you may come across several truncated fw log lines when trying to troubleshoot an issue. Or what about custom script :log messages? so now those are limited in max length (by a variable length) as well.
EXACTLY! Great reply! trying to keep something simple and quick, simple and quick (ie reading a log message), not add un-needed complexity + time
I like how there's something obviously wrong and people still defend it, saying that it's actually ok, and suggesting more or less complicated and not always practical workarounds. ;)
Syslog server is great, but is it argument against good log window in WinBox? No. If it would be, we could as well say that log window in WinBox is completely unnecessary and we can get rid of it, because external syslog is so much better.
Exporting log and opening it in favourite text editor, that's great too, sometimes. But not when you need to quickly see what's happening right now. Same for double clicking the line. If it's just one or two, fine. But if there's too many and new ones are coming one after another? Meh..
And if you have small screen or bad eyes, then what? Tough luck, no simple log viewing for you? Don't forget, WinBox recently added support for vertical scrollbars in windows, so that clearly shows they are not against small screens or big zooms. :)