📣 WinBox 4 is here 📣

Just for "fun"... the french keyboard lost more...

~ = AltGr + 2
# = AltGr + 3
{ = AltGr + 4
[ = AltGr + 5
| = AltGr + 6
` = AltGr + 7
\ = AltGr + 8
^ = AltGr + 9
@ = AltGr + 0
] = AltGr + <°>
} = AltGr + <+>

True, but that's annoying actually when reading on PC too. I'm not sure the printing press is right design metaphor. RFCs are single column and courier, perhaps that's a better metaphor. :wink:

The fact the list changes columns depending on packages/model is annoying. The same menu item could be in column 1, then column 2 on another router is rather annoying.

Normally giving folks choices is y'all thing, just not in WinBox. There should be an option to use "single column menus". I've hated the "3 column layout" since day one thousands of posts ago. And from the discussion, there seems to be a lot of people with big monitors and high DPI with plenty of room for one column.

So +1 for some option to allow "single column menus". If worried about cluttering options screen, I'd be fine if options were in a config file someplace.

Definitely if Winbox 4 will have more options for customization a lot of personal requirements from users for its behavior will be reduced, like having option for shortcuts key binding and this topic will be unnecessary if such option exists.

Even though ↓↗↓ -style arrangement is correct by itself, menu is not a book. When you read some book, you just read it line by line. When you open a menu, you look for a specific item. So, multi-column layout is absolutely awful, it's harder to find something, than in single-column layout.
Just add a setting to switch layout, as was suggested, in case someone likes this stupid layout. And single-column should be by default.

In books you can find "Index" that usually is multicolumn and lets you find things quickly.
The most crucial thing is to have it sorted what Winbox does.
If there is one long list, then extensive mouse movements are needed. Compact version lets protect us from the carpal tunnel syndrome :slight_smile:

In WinBox it's not so long to cause such problems.

Think that is because right margin of a listbox entries is clipped to the right main window margin.

Yes, it would be. My opinion against your. Both are equally as good or as bad. What is better: sparkling or still water?

Definitely a bug.

Added to the list of issues (#36), steps to reproduce are also described there: 📣 WinBox 4 is here 📣 - #2428 by teslasystems

And thus the need for options / settings to control these things — there does not have be only 1 way to do things.

Request: Login Options:

  • Safe Mode
  • Read Only

I know read-only can be set by user permissions and Safe Mode is available after login but often I want to login to check something and I know I don't need to make a change, currently I have a second user set up for that, but I'd rather just have it saved in my bookmarks file as a WinBox login option and then be able to turn it off if I need to change something- maybe this demotion could be built into RouterOS login.

Same with Safe Mode. It would be nice if a per bookmark preference could be saved, or else an application wide "Always start in Safe Mode" which is an option I would use every day for work on remote routers.

This is really an unnecessary discussion. A column layout is a widely used and well-established pattern. I would rather point out the inconsistency: the main level of the navigation is still single-column and expands vertically, while the second level spreads horizontally into multiple columns. But even that feedback would probably be very pedantic.

What do you mean by "column layout"? Multi-column or single-column? If first, I don't know, where this crap is established. All menus in OS and apps are single-column.

And I've already said, why multi-column is inconvenient :backhand_index_pointing_down:

You don't know a specific letter that each column starts from, so you need to do more seeking with eyes. Personally, I'm disoriented in this layout and it's very annoying.

So, let's MT just add an option and we'll end with this.

The issue isn’t with the multi-column layout, but with alphabetical order. When scanning a list that’s intended to be in alphabetical order, it’s natural to expect the items to follow that order. Multi-column articles don’t necessarily need to adhere to a strict order, but an ordered menu should. Therefore, the order must be preserved from line to line, rather than across columns.

Thx … that means it is a setting or works as designed ?

What's new in 4.0beta42:

  • macos: move away from Opt+key shortcuts to not mess with different languages
    • Opt+W -> CMD+W
    • Opt+S -> CMD+S
    • Opt+A -> CMD+Shift+S
    • Opt+F -> CMD+Opt+F
    • Opt+T -> CMD+T
  • ui: fix to prevent opening multiple instances of simple form setting windows (introduced 4.0beta31)
  • ui: fix dynamic confirmation popup width, when content smaller than buttons
  • ui: increase app max zoom limit 200% -> 250%
  • table: optimize table ui re-draw when reordering rows
  • table: add separators for status bar status elements
  • table: fix filter panel action button state when used together with quick filter
  • table: make quick filter popup width larger to fit longer names
  • settings: add option to change font rendering engine
    • by testing mostly useful for Windows users when swtiched to some system font
  • table: fix: focus find input field when clicked on find icon (sometimes didn't work in MacOS)
  • scale: fix zoom scaling for workspace popup and table search field
  • terminal: add support for Ctrl+left/right to move cursor by words
  • table: fix header comment wrapping in new line when it contains searched text
  • form: restore Collect checkbox fields in Torch panel in ROS6

@strods must be also restored AltGr on Windows, for exactly the same problem (to not mess with different languages),
(already tested also on 4.0beta42)
But also because some BASE characters are no longer available on Terminal.
It's not just a question of localization, but of actually writing BASE characters like { } [ ] # @ ` ~ | \ ^

Maybe a good idea to add the standard naming of keys, not everyone lives in the MacOS world…

Quoting myself:

Let's also remember that Windows and non-MacOS (Linux & Co.) account for about 85% of the market...
And that in terms of shortcuts, Linux is almost all identical to Windows...

And even if, hypothetically, 100% of the computers used by MikroTik staff are MacOS (which would explain a lot...),
that doesn't mean MikroTik staff should force everyone who uses non-MacOS (85%) to lower the quality of the user experience...

A thought:
I'd like to thank the MikroTik staff for their efforts to meet their own needs and those of others.
We're ALL always very critical about this, sometimes even too much,
but if the complainers are still here and haven't completely switched brands, it must mean something...

Thanks MikroTik.