📣 WinBox 4 is here 📣

More broadly, I'm not sure why "Alt" has to be ⌥/option key on Mac. IMO it should be ⌘/command, since on MacOS, unlike Windows, hitting the command/"windows" key does not bring up anything. While, ⌥/option does has different mapping depending on language, so it may not be just Polish that has overlaps. Additionally, as Mac user, using ⌥/option/"alt" is not very natural since no apps use it (for the previous reason, locale may effect them).

Now a big +1 on the <key>+G from terminal to WinBox suggested by @cggxannx above - great idea!

No - because Command matches Ctrl on Windows/Linux environment. Alt matches Option. Both match even by their names. Only difference is in their placement on keyboard (Mac vs others).

It is impossible to make both Alt and Ctrl to “match” Command…

Wow we are in Beta 41 and still missing a key feature that version 3.xx had for years. Which is: Be able to export and import the list of configured routers!!! Common Mikrotik, this is the major hold back unless I missed where in the GUI I can find it and do it.

Well, you can look in your user profile where this is stored and copy the relevant file…

The name is Addresses.cdb the location will vary depending on your OS.

Thanks, so in MacOS where is stored?

Also I am looking to have the same functionality within the GUI as version 3.x instead using special / hacky ways to do it.

I know it only for Windows and Linux. Don’t have MacOS.

No Worries, I just found the option on the latest beta

Case closed for me!!!

Yeah, you found the hidden "Actions"-menu. What a UX misconception.

Please bring back the Winbox3 function F6 to cycle the open windows to the top without other screens in between.

Even better: add some capability for “always below other windows” and “always on top” for individual windows, as commonly found in desktop environments (at least for Linux).

Reason for these: I always open a “Log” window and set it to full size, and then do all other work on top of that. When inadvertently clicking outside a window, the other open windows are concealed below the log window and painfully have to be brought forward one by one. In Winbox3 that was “easy” by doing repeated F6 presses but in Winbox4 it is much more difficult.

With the “always below other windows” attribute active, it would be possible to e.g. use the scrollbar of the log window without auto-raising it. Another option would be to require double-click to raise a window.

Half-fixed. While the order doesn't change anymore, some rule movements still occur (though actually they were not moved).

MultiDrag


Updated the list of issues: 📣 WinBox 4 is here 📣 - #2428 by teslasystems


And what a crap have you done with window list? Enormous area that uses 1/4 of a screen with a little amount of items in the middle, 'close all' button at the very bottom, and everything blurred and darkened? Seriously? Moreover, it's glitchy and shifts active window.

Usability = 0. Return everything back and fire your designer finally!


And one little thing about design, that I recently noticed.

Compare clear information about storage usage in WinBox 3

image

and this messy sh*t with no any separators and punctuation in WinBox 4

image

Looks like "used 48 %", because the word "used" if too far from what it actually belongs...

Currently it shows state, so icons are correct. Reversing will also require renaming to [:pause_button: Pause] / [:play_button: Resume] to represent action. Though, personally I'm ok with current state.

This new “fancy” window switcher does not work as an idea. Before you just could select needed window from the dropdown. Now when you click on that same icon you have to move away from there because window list is farther away and your actual workspace is obstructed by overlay with a preview of a single window. Yes contents of these overlay “previews” does update live, but it just confuses and obstructs. It would be better to revert to previous dropdown menu.

I had a bad flickering issue in Winbox 4 managed to fix it by disabling Windows 11 MPO in the registry.

Thanks for reminding about "flickering", I was preparing a post about it.

I've mentioned this problem earlier, but it shows up almost everywhere, so I wanted to emphasize it separately.
The problem is that painting mechanism works very bad and not optimized. When windows or their content are updated, the app performs many unneeded repaints, which not only uselessly consume computing resources and affect performance, but also cause artifacts.

Please note, that some of these issues are not always noticable to the eye, because these consequent repaints may happen quickly, the delay between them is quite random. You may need to open many different internal windows and in one (or all) of them issues will become visible.


Issues:

  1. Text in table headers is blinking sometimes while resizing the window. It means, that on each size change the new text is drawn right on the previous image buffer, that was not erased, and then everything is repainted again.
Headers blinking example

HeadersBlinking


  1. The window is repainted multiple times while changing the global scale. There are also artifacts and strange window width reduction:
Scaling artifacts example

ScalingArtifacts

  • Below is the same example by frames. You can see, that after reducing the global scale, the window is reduced according to the new scale and there is a text mess in table headers. After that, for unknown reason, window width is reduced. Looks like on the first repaint it's not yet calculated correctly, but on second repaint it's recalculated and repainted once again. (seems, that the issue with window width was fixed in beta41)

  1. [Fixed in beta42] This example was mentioned earlier, just repeating it to have everying in one place. When you drag some item in the ordered table, artifacts appear and elements (like text and 6-dot thumbs) are drawn right on the previous image buffer. Then one more repaint happens and artifacts disappear.
Item dragging example

Dragging


  1. Torch tool. It's supposed to update once per second. But in fact it updates randomly. Moreover, lines are absolutely not synchronized and update on their own. It causes a lot of repainting and significantly reduces overall performance. When you resize this window while the tool is running, there are stucks/freezes, it doesn't resize smoothly.
Torch tool updates example

TorchUpdates


Simple rule: if something needs to be updated, first recalculate everything (values, positions, sizes), draw them into a memory buffer and only after that copy this buffer to screen only once.


Some "offtopic" about Torch tool layout (and not only):
Just want to remind about stupid WB 4 UI again. In the Torch tool all fields are located on top, while 'Start' and 'Cancel' buttons are located on the opposite edge. When you need to stop the tool, change some filters and start again (and do it many times), you need to perform a "mouse dance", moving the cursor up and down through the whole screen height. And it brings even more "pleasure" when using touchpad.
The same can be said about newly introduced "genius" design of window list. Everything is scattered around and not usable at all.
WinBox 4 designers, have you ever tried to do anything serious using your product? Or go outside with small laptop when it's sunny, windy and frosty and do some diagnostics using your product? 100% sure, no. May be it's time to try? ...

:warning: Just follow WinBox 3 layout and don't reinvent a wheel! You are doing only worse and ruin everything that worked for years!

For your specific use case wouldn't a feature "move window to back" be more useful that iterating through all windows? For example some Ctrl+mouse-click on header? That would move Log back to background in 1 step.

Regarding shortcuts.

First of all remember that WinBox is a unique app, there aren't many that use such windowing system and include forms/tables/terminals.

Secondly global shortcuts cannot duplicate/interfere with window content shorcuts.

If we only are looking at MacOS system, then these shortcuts are 100% taken (by input fields or MacOS commands)
and can't be used by WinBox global shortcuts:
CMD+Q
CMD+A
CMD+Z
CMD+X
CMD+C
CMD+V
CMD+H
CMD+M

Shortcuts that also are "taken" by guidelines:
CMD+F (find)
CMD+G (find next)
CMD+T (open a new tab)

What combinations are we left with to be used "easily":
CMD+W/S/D/E/R

Global actions that we need in WinBox "ordered by priority":

  • close window
  • switch next window
  • switch previous window
  • global search
  • open new terminal

Potential future global actions:

  • expand/collapse window
  • open previously closed window
  • disconnect
  • some windows layout commands
  • open/switch workspaces

Even if we put 5 most important actions under CMD+W/S/D/E/R it doesn't feel right that these shortcuts affect global actions and other affect window content.

Vision is that
CMD+key affects only active window content (except of course MacOS global commands)
OPT+key affect global actions (including window management)

Are you no longer considering the other topic?


A list of all the existing keys in WinBox 3 should be made FIRST,
and that should be used as the default, so as not to "annoy" anyone who has been using WinBox for decadees (example, from 2007)...

Inevitably, everyone has their own preferences,
but the shortcuts inside the terminal certainly can't be the same outside...

On Windows, outside the terminal, I expect Ctrl+X, Ctrl+C, and Ctrl+V [⌘+X / ⌘+C / ⌘+V] to work like cut/copy/paste,
but I expect Ctrl+C [⌘+C] to not "copy" inside the terminal but break...
but Ctrl+V [⌘+V] on terminal must still paste the contents of the clipboard into the terminal.

Then to close the internal window, I expect Ctrl+F4 [⌘+F4], not a 5-finger combination...

Current WinBox 3 shortcuts

Windows/Linux MacOS Window Terminal Note
<INS> <?> Insert a new item in table or in multiple field [NOT implemented overwrite mode]
<DEL> <?> Delete selected items in table or in multiple field delete follow character
Ctrl+<+> ⌘+<+> Increase WinBox font / Zoom + =
Ctrl+<-> ⌘+<-> Decrease WinBox font / Zoom - =
<TAB> <TAB> Switch to next item autocompletion
Shift+<TAB> Shift+<TAB> Switch to previous item <nothing> (like just <TAB>)
Ctrl+<TAB> ⌘+<TAB> Switch to next tab Switch to next window
Ctrl+Shift+<TAB> ⌘+Shift+<TAB> Switch to previous tab Switch to previous window
F6 F6 Switch to next window =
Shift+F6 Shift+F6 Switch to previous window =
ESC <?> Close active window <nothing>
F4 F4 Close active window Toggle Safe Mode F4 for Safe only from v7
Ctrl+F4 ⌘+F4 <nothing> Close active window
F7 F7 <nothing> Toggle Hot-Lock Mode F7 only from v7
Ctrl+T ⌘+T <nothing> switch to active background task
Ctrl+A ⌘+A Select all go to line start
<HOME> <?> go to first line or item in dropdown go to line start
Ctrl+X ⌘+X Cut Toggle Safe Mode
Ctrl+C ⌘+C Copy BREAK script OR copy selected text
Ctrl+V ⌘+V Paste Paste from v6.4x.x
Ctrl+V ⌘+V Paste Toggle Hot-Lock Mode on old ROS only
Ctrl+Y ⌘+Y Redo inside a filed (not global redo) <nothing>
Ctrl+Z ⌘+Z Undo inside a filed (not global undo) <nothing>
Ctrl+E ⌘+E Enable active item go to line end
<END> <?> go to last line or item in dropdown go to line end
Ctrl+D ⌘+D Disable active item close terminal
Ctrl+M ⌘+M Edit active item Comment send current command line
F1 F1 <nothing> general console usage help
F2 F2 Edit active item Comment <nothing>
F3 F3 go to Find field, find next only on v7 do the same as Ctrl+R / ⌘+R
Ctrl+R ⌘+R <nothing> I do not know what do this shortcut only on v7
Ctrl+N ⌘+N <nothing> next command on history
<DOWN> <?> move between fields next command on history
F5 F5 <nothing> clear terminal window
Ctrl+L ⌘+L <nothing> clear terminal window
Ctrl+P ⌘+P <nothing> previous command on history
<UP> <?> move between fields previous command on history
Ctrl+H ⌘+H <nothing> delete previous character
Ctrl+B ⌘+B <nothing> go to previous character
<LEFT> <?> move between fields go to previous character
Ctrl+F ⌘+F <nothing> go to next character
<RIGHT> <?> move between fields go to next character
Ctrl+K ⌘+K <nothing> delete till the end of line
Ctrl+I ⌘+I <nothing> is like <TAB> to list possible commands

Yes that would also be a great option. But that has never been present in winbox, while F6 was present and a useful alternative. I think F6 was much better than any Alt+letter combination because it is much easier to enter it, without causing finger cramp. Please use function keys (or have them as aliases) instead of Alt-key combinations whenever possible.

Plain function keys can not really be used by global shortcuts. They need to be sent via terminal. There are command like tools that use these keys and so do not work on WB3 (remember than you can ssh in any system). Also RouterOS console maybe will use other functional keys in future. So only CTRL+functionkey is safe to use.
How is Alt+S hard to press?

If by unique you mean it follows standard Windows "MDI" (multiple document interface) app from the 1990s. :slight_smile:

Now since MDI was always an anti-pattern in Mac UI guidelines, that does means there are no standard shortcuts on Mac for in-app "sub-windows" — so I get this a tricky problem.

While I guess it wouldn't effect me since I use the English locale on Mac, a standalone ⌥/option is generally used as a "unicode accessor", so I worry that some non-english locale might conflict (even if English does not) so it too is limited in possibilities.

The typical Mac solution is to use chords like shift/ctrl/option along with the ⌘ command. While I don't find ⌥ S "hard", I worry the scheme breaks down as more are added and it pretty non-standard to use option/⌥ alone as a shortcut.

I'm still of the opinion y'all are trying too hard for commonality between platforms. While good generally, I'm not sure that work with the keyboard shortcuts. For example,

@pe1chl is totally right for Windows using function keys make sense - but on Mac "functions keys" are all assigned, so F[1-12] is far from ideal and requires the fn key. While Option+Command are next to each other on the typical Mac keyboard and common to use together for shortcuts, but that is not true on Windows.

But I think my main suggestion be:
In any case, there should be some dialog/window that shows the current shortcuts in the WinBox UI
... since no one is "guessing" these & finding them in this 3K post thread I assure you is not easy (nor does someone want to search Confluence to find them eventually)