Emmm... What's wrong with WB 3 on 150 % scale? I also have the same scale and don't see any significant issues. Of course, scaling should be done by the app, not by Windows, because it just stretches a bitmap. Btw, OS scaling can be performed only by bitmap stretching and will always be "sucky". Anything else is impossible and won't work correctly. Scaling should be completely handled by the app for good appearance.
Most of us are not using Windows XP anymore…
How Windows XP is related to that? Looks like you don't know how scaling works.
I already wrote about this: 📣 WinBox 4 is here 📣 - #1887 by teslasystems
I think it is you who doesn’t know how scaling works in modern operating systems…
Windows (and Linux) do not first render the characters and then enlarge the bitmap anymore, they render the characters larger. How well that works depends on the font and things like anti-aliasing and subpixel hinting, but it isn’t bitmap scaling, that was in the XP days.
Reread the link above... If the app is DPI-aware, OS doesn't play any role in scaling, everything is performed by the app, including setting a correct font size. For DPI-unaware apps, OS just stretches them. The Dude is a good example (though the map is rendered by the app itself and not stretched).
Hi,
Thanks for the suggestion, however I cant make that work either. Here is the outcome (raspberry pi os debian trixie on pi 5). After what you see in that log on the console, no gui pops up.
alex@pi-desktop:~/Apps/Winbox $ box64 ./WinBox
[BOX64] Box64 with Dynarec v0.3.4 nogit built on Apr 24 2025 09:54:47
[BOX64] Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL ATOMICS SHA1 SHA2
[BOX64] Running on Cortex-A76 with 4 cores, pagesize: 16384
[BOX64] Will use hardware counter measured at 54.0 MHz emulating 3.4 GHz
[BOX64] Detected 48bits at least of address space
[BOX64] Counted 63 Env var
[BOX64] Library search path:
[BOX64] Binary search path: ./:bin/:/usr/local/sbin/:/usr/local/bin/:/usr/sbin/:/usr/bin/:/sbin/:/bin/:/usr/local/games/:/usr/games/
[BOX64] Looking for ./WinBox
[BOX64] Rename process to "WinBox"
[BOX64] Using native(wrapped) libxcb-glx.so.0
[BOX64] Using native(wrapped) libEGL.so.1
[BOX64] Using native(wrapped) libdl.so.2
[BOX64] Using native(wrapped) libGL.so.1
[BOX64] Using native(wrapped) libz.so.1
[BOX64] Using native(wrapped) libfreetype.so.6
[BOX64] Using native(wrapped) libfontconfig.so.1
[BOX64] Using native(wrapped) libexpat.so.1
[BOX64] Using native(wrapped) libX11.so.6
[BOX64] Using native(wrapped) libxcb.so.1
[BOX64] Using native(wrapped) libXau.so.6
[BOX64] Using native(wrapped) libXdmcp.so.6
[BOX64] Using native(wrapped) libxkbcommon.so.0
[BOX64] Using native(wrapped) libxkbcommon-x11.so.0
[BOX64] Using native(wrapped) libxcb-icccm.so.4
[BOX64] Using native(wrapped) libxcb-image.so.0
[BOX64] Using native(wrapped) libxcb-keysyms.so.1
[BOX64] Using native(wrapped) libxcb-randr.so.0
[BOX64] Using native(wrapped) libxcb-render-util.so.0
[BOX64] Using native(wrapped) libxcb-shm.so.0
[BOX64] Using native(wrapped) libxcb-sync.so.1
[BOX64] Using native(wrapped) libxcb-xfixes.so.0
[BOX64] Using native(wrapped) libxcb-render.so.0
[BOX64] Using native(wrapped) libxcb-shape.so.0
[BOX64] Using native(wrapped) libxcb-xkb.so.1
[BOX64] Using native(wrapped) libX11-xcb.so.1
[BOX64] Using native(wrapped) libm.so.6
[BOX64] Using native(wrapped) libpthread.so.0
[BOX64] Using native(wrapped) libc.so.6
[BOX64] Using native(wrapped) ld-linux-x86-64.so.2
[BOX64] Using native(wrapped) libutil.so.1
[BOX64] Using native(wrapped) librt.so.1
[BOX64] Using native(wrapped) libbsd.so.0
APP,INFO: version: "4.0beta35"
PERS,WARN: read error opening "No such file or directory" "/home/alex/.local/share/MikroTik/WinBox/settings.cfg.viw2"
APP,INFO: loading addrs db from: "/home/alex/.local/share/MikroTik/WinBox/Addresses.cdb"
PERS,WARN: read error opening "No such file or directory" "/home/alex/.local/share/MikroTik/WinBox/Addresses.cdb"
Any ideas?
Thanks,
Alex
I'd try creating the directory,mkdir -p /home/alex/.local/share/MikroTik/WinBox as the error suggest it's can't read that directory. Perhaps permissions on /home/alex/... are blocking your own account, although that be atypical since it's your home directory.
Thanks,
I have done as you suggest, no change. My understanding is those are warnings and are typical on first run of winbox, and they will be ccreated once its run, so I dont think its the issue. The issue is that the GUI never shows up though the app doesnt quit and I have to quit it with CTRL-C
Best,
Alex
Hi, can the first post be updated at each time like for routerOS releases ?
1 Like
Noticed some strange behavior with beta39 on macOS. When I clicked the edge of a window to resize it, the opposite side seems to have gone as far as possible in the other direction, and completely outside the bounds of the main Winbox window itself. Fixing this was tedious as it required me to shrink the inner window, then drag it back to the visible area in Winbox, and then shrink some more, and repeat this maybe 5-10 times just to get the inner window to fit within the main Winbox window.
I also noticed the pointer become “out of sync” with Winbox while dragging a window around inside of it. When I dragged the window around and then released the drag, my pointer was not “holding” the same location on the window that it started; it was shifted away from the spot that I had initially “grabbed.”
I’m going to try to get screen recordings of both behaviors but they don’t seem to be consistent, so I’m trying to determine what is required to reproduce.
The ability to pick my own font is great, although I would love to have different fonts used for different things… the data rows and fillable fields displayed in most windows, along with all Terminal windows, should be a fixed-width font (to help show where there are spaces or differentiate 0 from O), but the menus and tabs and window decorations are OK to be different, variable-width fonts. Having labels and menus be fixed-width just makes them take more space without a big gain in usability, at least for me.
One other consistent and annoying bug (this has been around for several versions, possibly since the beginning) I’ve found is that after clicking the “Find” button, the text-input focus is not automatically moved to the new Find input box. This is super annoying since you expect to be able to type into that Find box after clicking Find, but first you have to move your mouse and click into the Find box before you can actually type what you want to search for. I notice it the most on the initial connection manager window, where I rely on Find because I have 350+ saved connections to deal with…
Not a biggie, just annoying…
Could someone who uses RoMon please try logging into that device by double-clicking the instance in RoMon Neighbours?
For me this doesn’t appear to launch the RoMon instance where a few point releases back it did. Seems to now require a user to click Connect. Much easier to double click the istance in RoMon Neighbours.
Using Linux, Debian13 KDE.
It's Segoe UI in WinBox 3 too, but the default font size is different, and it has the "grid fit" hinting, so the rendering snaps to the pixel boundaries.
In WinBox 4 the default size is different (larger), thus, in order to have the information density from WB3 we have to reduce the scaling factor, which in turn makes the font size some non-integer value.
On my 96dpi 1440p monitors I am doing this, and it improves a bit compared to your screenshot:
-
Run Windows' ClearType Tuner, adjust the settings to suit your monitors.
-
Create a
qt.conftext file and put it in the same folder as theWinBox.exeexecutable with the content:[Platforms] WindowsArguments = fontengine=gdiThis make QT uses DirectWrite instead of FreeType, and it will respect the tuning for ClearType.
-
In WinBox set Custom font to
Segoe UIand Global zoom to92%.
The font weight is still a bit too much though.
1 Like
Works as expected on Windows 11.
In addition to GUI zoom, I think it would be good to allow changing the "base font size". This is how web browsers handle it, and websites that respect this setting adjust their font sizes relative to the base size.
1 Like
After the upgrade, not changing scaling (92%), many of my customized column widths are again “too narrow”. I had set them correctly on the previous version.
It may be because of the changed font? It now is set to “Manrope MD” and I think it was “Segoe UI” before?
Anyway, this kind of thing is very annoying. It is a lot of work to fixup all those workspace files again, especially because they are closed and I cannot write some tool that does it for me. (like setting some desired width for all columns of some type or name)
Pretty sure that would be Arial.
And one more thing that comes to mind: since the latest beta, you can change the UI font. I'd suggest having at least:
- A variable-width font (mainly for the UI)
- A monospace font (for the terminal and other places where a fixed-width font makes sense)
It might even be useful to let users adjust the "font assignment". For example, a regular Noto Sans could work well for the UI, while JetBrains Mono might be easier to read in tables.
It wasn't mentioned in the changelog, but now columns selection dropdown had become full-height, as I suggested. Thank you for hearing!
Tested new scaling.
There are still some problems, but most of the fundamental issues were fixed. Overall good job 
-
Newly added "scaling settings" window doesn't change its size together with global zoom. Probably, it was done intentionally, because otherwise it will jump away from the mouse, when you change scale. But on High-DPI screen it's quite small. I think it could be made larger. Or may be use OS scale for this window, so it will have a normal size for all cases.
-
Newly added "scaling settings" window disappears, if you click somewhere. Very inconvenient, when you adjust optimal values! Just add close button to it, so it can be closed, when the user needs to close it.
-
Removing current scale value and +/- buttons from the settings window doesn't appear to be a good idea. Now, to see current scale, you need to do more clicks and open this new scaling settings window.
I would suggest:
- return current scale value to settings window (or even better to the main toolbar)
- add +/- buttons to the new "scaling settings" window for precise adjustment. Just trackbars without precise control are not convenient (btw, still waiting for arrows in scrollbars...).
- Workspace dropdown menu doesn't change its width together with global zoom and this causes drawing issues. Same problem with 'Find' textbox, it doesn't follow global zoom value.
-
[Fixed in beta41] Was already mentioned by @CGGXANNX (📣 WinBox 4 is here 📣 - #2888 by CGGXANNX), there are issues with text selection in Terminal on some scales. Selection doesn't follow the mouse precisely in vertical direction.
-
Would be nice if the app will apply current OS scale, when launched for the first time.
-
Reducing maximum scale limit to 200% is not good either, consider increasing it to 500% (this is the maximum value on Windows OS).
Also updated the list of regular issues: 📣 WinBox 4 is here 📣 - #2428 by teslasystems
Can we have inline comments like the 3.x version has?
2 Likes