Normis, does this mean that Winbox will honor the scaling setting so that I don’t have to zoom every time I open a new session?
Thanks!
So am I ![]()
for what exactly ?
btw. still no native version for mac and linux, still no shortcuts implemented
,
otherwise - thanks for new version, is great, appreciated…
add ctrl+c ctrl+v in the console
Ctrl+C already works for aborting commands. But it could probably have double use, where copying would work when there’s some selected text. Or there are also safe non-conflicting Ctrl+Ins and Shift+Ins (my favourite, but those currently don’t work in Terminal either).
Shift+Ins in Terminal works at least in Wine for MacOS.
Great, that’s half of the work done. It would be real shame to not add Ctrl+Ins now. ![]()
I would still very much like to see the following changes:
- easier widget for selection of columns (a modal panel with checkmarks for all possible columns in a “square” layout where multiple checkmarks can be toggled before clicking OK)
- some way to raise windows that are covered by another window that has opened on top of it, e.g. a set of “window buttons” in the dashboard bar or some mouse action to “lower” the current window so other existing windows may appear on top of it.
Agreed, takes way to much effort to deselect all the FP* columns, across multiple forms.
Good day.
Some new bugs:
- interface window resises to default size, even afer manual resize.
- same for partition window.
Not here…
Same here. I experienced this resizing for the first time since switching to Winbox 3.22 (64 bit).
Moving items and changing column widths has become unstable!
When moving an item or changing a column width and keeping mouse button pressed for a while to find new suitable position, it suddenly jumps to completely wrong position.
I think this happens when the screen is updated in the meantime, e.g. to show updated counters in firewall view.
Weird… Plus auto windows resize…
I am waiting for a fix…
Same here on Windows 10. Also the last (and most important one) line of the log is very hard to read - it almost always stay “between” lines, auto scroll doesn’t always work. I hope that bugfix version will be released.
Can I just make a suggestion here? Why not re-write Winbox with something like Qt framework? It has all this Hi-DPI nonsense already solved.. it’s built in. Bonus: Winbox would become cross-platform! I guess it couldn’t be called Winbox anymore, huh?
Yes, I’m seeing that too. Most irritating.
how do i get winbox old version?
emils

I still must run WinBox 6.4 for manage old ROS v5.26 who cannot be upgraded to v6.x family.

.
*) added scroll bar support in item property windows;
It’s still not that mouse scroll ![]()

Then what mean this point ??
Old bug with firewall chain’s popup still exiting monitor

.
*) use monospace font for big pop-up messages;
It;s to big, but font it’s now monospace like CLI, thanks!.

.
other
Logs with Filtering and Searching feature are awesome!.
CTRL+G not select the current entry log and you not know what rule is currently selected !

What is WinBox 6.4?
Anyways, RouterOS 5 requires WinBox DLLs to be downloaded from the router. That was removed in WinBox 3.13 (and for a reason!) and has nothing to do with this “legacy connection mode”.
By the way, what stops you from upgrading from RouterOS 5.x?
*) added scroll bar support in item property windows;
It’s still not that mouse scroll
Then what mean this point ??
Property windows are not drop-down menus. Property window is what opens when you double-click on an item in the interface list, or a rule in the firewall rules window, etc.
And scroll bar is not a mouse wheel either!