📣 WinBox 4 is here 📣

shahro0z · Sun Nov 24, 2024 10:16 am

Using shift + click to select multiple items in lists does not update the number of selected items in the top right corner of each windows while clicking in the check box one by one does work.

stmx38 · Sun Nov 24, 2024 2:23 pm

Where's the close/exit button in the new Winbox v4 client? All I see is "New WinBox" and the ellipsis that just shows settings.

When we are connected to the RouterOS, exit button is located in the top right corner.

Screenshot 2024-11-24 at 14.18.37.png

Mon Nov 25, 2024 1:57 pm

How do i import saved session to new winbox4

Use the menu item called "import" on the right side.

k2dI5umrD9VO · Mon Nov 25, 2024 9:10 pm

Where's the close/exit button in the new Winbox v4 client? All I see is "New WinBox" and the ellipsis that just shows settings.

When we are connected to the RouterOS, exit button is located in the top right corner.
Screenshot 2024-11-24 at 14.18.37.png

Thanks, but there's no indication of what the button is/does. If I hover over it, no dialog box appears telling me it's "Exit" or "Disconnect".

kiler129 · Tue Nov 26, 2024 12:23 am

Thanks, but there's no indication of what the button is/does. If I hover over it, no dialog box appears telling me it's "Exit" or "Disconnect".

This is a known issue, described in the first post as "Many UI buttons need Hover help text".

Use the menu item called "import" on the right side.

Does the import imply that Winbox4 uses a different database location? I have old winbox specifically backed up.

Tue Nov 26, 2024 8:19 am

Yes, can have to import old format files (CDB), and you can also use the Open button, to use the Winbox 3 files. But in this case, some character encoding issues could happen. If you only plan to use Winbox 4, better import and use the new one.

infabo · Tue Nov 26, 2024 9:40 am

:::::::: Important notice. We are using the Qt framework, as you probably know, but Qt is dropping support for macOS 11 and earlier. We do need to upgrade Qt, to fix the known performance issues in Windows, slow log scrolling etc. People with older Apple computers than 2014-2015. will not be able to upgrade. It is possible to upgrade some of them to macOS 12 in unofficial ways, we can post a tutorial if many people are affected by this. ::::::::::::

I have reported the beta12 crashing on startup on macos 11.7 last week or so. Just received an answer from support: "We will see what we can do".

Interesting.

Tue Nov 26, 2024 10:26 am

We tried to override Qt limitations, but does not look promising. You will have to use OpenCore patcher to upgrade to macOS 12

infabo · Tue Nov 26, 2024 11:11 am

Depends on the Qt version. 6.5 LTS still supports macos 11. 6.8LTS support macos 15.

Well played. Finally Mikrotik tooling has to move with industry.🙀

Tue Nov 26, 2024 11:12 am

Yes, it fixes Windows issue with slow UI

SignumFera · Tue Nov 26, 2024 1:20 pm

Dont see this listed in the first post.

Just tested in Winbox 4 Beta 12, still broken. Am I the only one with this issue. No one else loading large routing tables in ROS6?

Thanks for the work so far, looking great.

ROS6 with large routing tables comes up with an empty route list

Winbox 4
Screenshot_20240913_132856.png

Winbox 3
Screenshot_20240913_133032.png

Kind regards

jonmansey · Tue Nov 26, 2024 10:11 pm

Please make the log window tail the log by default. I.E. if it's set to sort top down with the most recent log entry at the bottom, then the log window should open pre-scrolled to the bottom and tailing the new log entries. It should also remember if I set it like this and when I log back in, the log window should already be tailing the log properly. winbox3 does this just fine. Im surprised it's not more of a priority feature/function/bug in W4. Right now the first thing I have to do every time on every device I log into is scroll to the end of the log window dragging the almost invisible scroll button. Even then, if you have less than the default 1000 lines in the log, it doesnt auto-scroll as new log entries are created. Broken in multiple ways compared to the winbox3 default behavior, which suited just fine.

Edified · Wed Nov 27, 2024 1:08 am

Layout Issue. It wouldn't be so bothersome if the password field was already focused.

Screenshot 2024-11-26 at 2.17.44 PM.png

Also I think there's no contrast or outline no the password field, just white on white, which is weird.

Edified · Wed Nov 27, 2024 1:13 am

Loving the dividing lines and hover effect, much much easier to see what is an expandable header:

Screenshot 2024-11-26 at 3.11.59 PM.png

And the nav-on-right makes everything FASTER!

Edified · Wed Nov 27, 2024 1:19 am

MacOS: If you have renamed the Application, for example to "Mikrotik Winbox.app" or "Winbox 4.app", the auto-update fails.

Not huge but it used to work in previous betas.

Also the "Release notes" text layout is a little funky:

Screenshot 2024-11-26 at 2.16.18 PM.png

Edified · Wed Nov 27, 2024 1:28 am

Would love to see the saved list Select from: field get the ability to load multiple address files like:
- Neighbors
- RoMON Neighbors
- Saved Addresses
- Some Other File
- Some Other Other File

The address files could all be in a particular directory. This would mean we could have different passwords for different files, different files for different purposes, the ability to sync a work file and not mess with or have to merge or swap a home file, or even keep an unprotected file.

And I would love to see the Select from: Pull Down get the same interface treatment as the other parts or Winbox4:

Screenshot 2024-11-26 at 3.26.38 PM.png

(Neighbors/Bookmark Files in this exact style)

spippan · Thu Nov 28, 2024 2:14 pm

How do i import saved session to new winbox4

right click the space in "Saved" view

28_11_2024.png

Thu Nov 28, 2024 2:17 pm

Layout Issue. It wouldn't be so bothersome if the password field was already focused.
Screenshot 2024-11-26 at 2.17.44 PM.png
Also I think there's no contrast or outline no the password field, just white on white, which is weird.

passwords are not oficially implemented yet. this only shows up if you open a winbox3 file that had encryption. when we add encryption in winbox4, we will address this .

jrbarna · Thu Nov 28, 2024 11:04 pm

is there any search option in lists (like Ctrl+F to find something quickly), or just I can't find it?

frayoshi · Fri Nov 29, 2024 4:11 am

Want to report that files cannot be mouse moved on the 'Files' > 'File List' tab.
i.e. backups can be created, but not reassigned to a persistent directory.
Version: 4.0beta12
on Wayland (Hyprland)

frayoshi · Fri Nov 29, 2024 4:13 am

Also report that for some reason, the numlock gets constantly deactivated while using the program, but this might be a Wayland only thing, and not sure if related.
Still, maybe others might have experienced it (?)

v. 4.0beta12
Wayland (Hyprland)

Fri Nov 29, 2024 11:06 am

is there any search option in lists (like Ctrl+F to find something quickly), or just I can't find it?

Filter button in top right corner of each inner window

teslasystems · Fri Nov 29, 2024 3:02 pm

What about grid lines? Are you going to add them? The interface is not clear without them.

homerouter · Fri Nov 29, 2024 7:58 pm

Don't understand why v4 should be so different in layout, compared to v3?
For me, ver 3 is just the best. The overview is completely gone in v4, in my opinion.
Maybe it's just me who is too negative, but v4 won't be used until v3 disappears from the MT site.
I use winbox under windows...

veso266 · Fri Nov 29, 2024 10:46 pm

Is this suppose to work on Windows 7?
Because for me it needs dxgi.dll as well as
SetThreadDescription
GetCurrentPackageFullName
from kernel32.dll

AdjustWindowRectExForDpi
AreDpiAwarenessContextsEqual
from user32.dll

api-ms-win-core-synch-l1-2-0.dll
api-ms-win-core-winrt-l1-1-0.dll
api-ms-win-core-winrt-string-l1-1-0.dll

which windows 7 doesn't have, meaning winbox 4 doesn't run
the latest 3 (v3.41) works fine

I do prefer winbox v3 but I am afraid that in the future I will not be able to use Winbox v3 anymore because newer RouterOS will not support it anymore, meaning I will be forced to not update my routers, which I realy don't want to do

PS: Before anyone asks, why I still use windows 7
1. I use some custom hardware with drivers that don't run on anything newer
2. I like Aero
3. I need Microsoft Virtual PC 2007, which doesn't run on anything newer then Windows 7

I do prefer winbox v3 gui anyway, so I will probably not even use v4, but still it would be great if it would run

Amm0 · Fri Nov 29, 2024 11:13 pm

I do prefer winbox v3 but I am afraid that in the future I will not be able to use Winbox v3 anymore because newer RouterOS will not support it anymore, meaning I will be forced to not update my routers, which I realy don't want to do

Mikrotik could comment on this.... But that may not necessarily be true. AFAIK winbox generates the UI based on metadata on the router, so I'm not sure winbox3 and winbox4 be different. Now if they add help or wizards to winbox4 in future, that's where the differences might be.

pe1chl · Sun Dec 01, 2024 1:36 pm

Maybe one of the outside-MikroTik users who have found detailed information about how the system works could reveal some detail about that.
I would expect that RouterOS has some tables of available commands and options and directives for the GUI (webfig/winbox) which are used by the generic command interpreter and the webfig and winbox interfaces. It is not like when a new command is added, someone adds some code with a strcmp(cmd, "newommand"), no, the new command is added to some data structure and when it is typed some function specified in that structure is called.
However, many times when a new command is added it is first available only in command mode and later appears in the GUI. So this data structure isn't as well integrated as one would expect it to be, maybe for historical reasons going back to the first release?
It seems a bit like there are separate data structures for use by the command interpreter and and for use by the GUI, and often the developers of new functionality first add it to the command table only and later someone (else?) adds an entry in the GUI tables.
Also, with v7 apparently some new functions have been added in a different way than everything worked in v6, and they still do not integrate well with winbox, v3 or v4.
E.g. the routing table and the BGP sessions table are not correctly refreshed in winbox anymore, one sometimes has to completely close winbox and establish a new session to get accurate data. Assumptions of what can be cached apparently have been violated, and also some automatic timed refreshes no longer work.
It would be interesting to see why that is and why it takes so long to fix.

engycz · Sun Dec 01, 2024 10:00 pm

Scrolling with two fingers on the touchpad is nearly unusable. When moving fingers slowly, the window content does not scroll, and when moving fingers at normal speed, it scrolls very slowly.

Winbox 4.0beta12
Windows 11

Mon Dec 02, 2024 8:18 am

Don't understand why v4 should be so different in layout, compared to v3?
For me, ver 3 is just the best. The overview is completely gone in v4, in my opinion.
Maybe it's just me who is too negative, but v4 won't be used until v3 disappears from the MT site.
I use winbox under windows...

You can keep using Winbox3 if it is perfect for you

gigabyte091 · Mon Dec 02, 2024 8:29 am

I noticed that sometimes when clicking "new winbox" instead of opening a new window everything closes. Not every time but 1 in every 6-7 times it crashes.

Mon Dec 02, 2024 11:31 am

What's new in v4.0beta13:

*) implement opened windows list
*) implement global menu search
*) bump minimal macOS version to 12.0, because 11.0 is EOL and dropped by Qt
*) accept button with Enter/Return keys also on Windows and macOS
*) fix max u32 value processing on some fields
*) fix visual 1px bug in form's anchor panel
*) move form tab's icon to left side to not overlap with scrollbar
*) fix table comment column when in wrapped mode
*) make focused button element border more accented

Mon Dec 02, 2024 11:41 am

Please implemnt column vertical divider lines as it's much easier to read data and recognize where one info ends and a new one starts.

wispmikrotik · Mon Dec 02, 2024 11:47 am

What's new in v4.0beta13:

*) implement opened windows list
*) implement global menu search

Very thanks.

Regards,

Mon Dec 02, 2024 11:50 am

Please implemnt column vertical divider lines as it's much easier to read data and recognize where one info ends and a new one starts.

Agree.

On Windows 11 you can't really see it unless you start hovering over the area with your mouse. Inefficient.

eddieb · Mon Dec 02, 2024 12:02 pm

nice to see the opened windows list back !

maigonis · Mon Dec 02, 2024 12:15 pm

It would be nice to have a "force reconnect" button, as sometimes session hangs and do not recover, so I have to close and open session again.

nmt1900 · Mon Dec 02, 2024 2:21 pm

Lateral scrolling finally works!

spippan · Mon Dec 02, 2024 2:29 pm

What's new in v4.0beta13:

*) implement opened windows list
*) implement global menu search
*) bump minimal macOS version to 12.0, because 11.0 is EOL and dropped by Qt
*) accept button with Enter/Return keys also on Windows and macOS
*) fix max u32 value processing on some fields
*) fix visual 1px bug in form's anchor panel
*) move form tab's icon to left side to not overlap with scrollbar
*) fix table comment column when in wrapped mode
*) make focused button element border more accented

great little improvements step by step. much appreciated!
especially the "opened windows list" and "global search"!!! awesome

now waiting on
- vertical lines in form view
- rearangable columns (!)
- WoL quick-link from dhpc-leases (;
- and of course "Open in new window"

edit:
noticed the winbox4 start window now remembers my selection on "Saved:" and "Neighbors:" - thanks a lot

Amm0 · Mon Dec 02, 2024 5:01 pm

*) implement opened windows list

Thanks. One subtle thing is the "keyboard help" shown at bottom should use the platform-specific terms for "Alt", which on Mac be "Option" or the ⌥ symbol.

OptionNotAlt.png

w0lt · Mon Dec 02, 2024 5:53 pm

What's new in v4.0beta13:

*) implement opened windows list
*) implement global menu search
*) bump minimal macOS version to 12.0, because 11.0 is EOL and dropped by Qt
*) accept button with Enter/Return keys also on Windows and macOS
*) fix max u32 value processing on some fields
*) fix visual 1px bug in form's anchor panel
*) move form tab's icon to left side to not overlap with scrollbar
*) fix table comment column when in wrapped mode
*) make focused button element border more accented
great little improvements step by step. much appreciated!
especially the "opened windows list" and "global search"!!! awesome

now waiting on
- vertical lines in form view
- rearangable columns (!)
- WoL quick-link from dhpc-leases (;
- and of course "Open in new window"

edit:
noticed the winbox4 start window now remembers my selection on "Saved:" and "Neighbors:" - thanks a lot

Also, please put the "Exit" selection back in the menu.. :-)

maigonis · Mon Dec 02, 2024 7:27 pm

Encryption should be in one style.

Screenshot_20241202_192545.png

jonmansey · Mon Dec 02, 2024 7:51 pm

Log window auto-scroll "tail the log" now seems to be working in beta 13, great!

Now if it would just remember that I had it scrolled to the end when closing and re-opening session.....or default to scrolled to the end if sorted ascending.

minelli · Mon Dec 02, 2024 10:06 pm

Good afternoon, I've been having problems with winbox 4 since I updated to beta 12 and beta 13. It doesn't open on BigSur. Here's the error log for analysis.
In beta9 version it was working normally.

Process:               WinBox [6138]
Path:                  /Applications/WinBox.app/Contents/MacOS/WinBox
Identifier:            my.example.com
Version:               0.1 (0.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           WinBox [6138]
User ID:               501

Date/Time:             2024-12-02 16:58:49.069 -0300
OS Version:            macOS 11.7.10 (20G1427)
Report Version:        12
Anonymous UUID:        D4F5F1A5-CE7B-4212-958F-4C0F4EF6E079


Time Awake Since Boot: 11000 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x4] Symbol missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Symbol not found: _kIOMainPortDefault
  Referenced from: /Applications/WinBox.app/Contents/MacOS/WinBox
  Expected in: /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
 in /Applications/WinBox.app/Contents/MacOS/WinBox

Binary Images:
       0x107c84000 -        0x10a5ddfff +my.example.com (0.1 - 0.1) <9B222467-FD61-3729-8073-AF1477B910CD> /Applications/WinBox.app/Contents/MacOS/WinBox
       0x113015000 -        0x1130b0fff  dyld (852.2) <BD607394-9008-33B9-B98B-A5886668E52C> /usr/lib/dyld
    0x7fff203b7000 -     0x7fff203b8fff  libsystem_blocks.dylib (79) <F5B25F38-FC21-3BF5-A147-3B913DA098BE> /usr/lib/system/libsystem_blocks.dylib
    0x7fff203b9000 -     0x7fff203eefff  libxpc.dylib (2038.120.1.701.2) <151C64CA-CA6F-3989-A558-796EB6ED0C11> /usr/lib/system/libxpc.dylib
    0x7fff203ef000 -     0x7fff20406fff  libsystem_trace.dylib (1277.120.1) <1F20357C-395F-3095-B525-AD9403290A92> /usr/lib/system/libsystem_trace.dylib
    0x7fff20407000 -     0x7fff204a4fff  libcorecrypto.dylib (1000.140.4) <BDD3FF5E-34F8-3AC0-A05C-F9AC17C88BBF> /usr/lib/system/libcorecrypto.dylib
    0x7fff204a5000 -     0x7fff204d1fff  libsystem_malloc.dylib (317.140.5) <3AB4C7E9-C49C-3EB7-9370-370F3F655024> /usr/lib/system/libsystem_malloc.dylib
    0x7fff204d2000 -     0x7fff20516fff  libdispatch.dylib (1271.120.2) <5D824C33-C5E2-38A8-BD00-D934443DBDAB> /usr/lib/system/libdispatch.dylib
    0x7fff20517000 -     0x7fff20550fff  libobjc.A.dylib (824.1) <A0961DED-3477-3856-A6BC-CFE2475CB2F4> /usr/lib/libobjc.A.dylib
    0x7fff20551000 -     0x7fff20553fff  libsystem_featureflags.dylib (28.60.1) <2BAC8770-AFC8-3FE2-B6C6-27CE44B2B2BA> /usr/lib/system/libsystem_featureflags.dylib
    0x7fff20554000 -     0x7fff205dcfff  libsystem_c.dylib (1439.141.1) <BC8BCEEA-CA52-32C7-9FF5-E444CF9EF66A> /usr/lib/system/libsystem_c.dylib
    0x7fff205dd000 -     0x7fff20632fff  libc++.1.dylib (905.6) <5BA6B5ED-7842-3B13-86B0-00EB511CE2FE> /usr/lib/libc++.1.dylib
    0x7fff20633000 -     0x7fff20648fff  libc++abi.dylib (905.6) <B96FC1DD-0056-3E11-862A-C0BB8239FEA0> /usr/lib/libc++abi.dylib
    0x7fff20649000 -     0x7fff20678fff  libsystem_kernel.dylib (7195.141.49.702.12) <BA061E84-6D44-3037-832D-E86D783FA917> /usr/lib/system/libsystem_kernel.dylib
    0x7fff20679000 -     0x7fff20684fff  libsystem_pthread.dylib (454.120.2.700.1) <409239A7-2E4E-31C7-87EB-EE50B7981204> /usr/lib/system/libsystem_pthread.dylib
    0x7fff20685000 -     0x7fff206c0fff  libdyld.dylib (852.2) <FD8DB5BC-F199-3524-9DC4-DAEC0E94712F> /usr/lib/system/libdyld.dylib
    0x7fff206c1000 -     0x7fff206cafff  libsystem_platform.dylib (254.80.2) <52A77346-8AA5-3BB7-906D-C7503B491CF9> /usr/lib/system/libsystem_platform.dylib
    0x7fff206cb000 -     0x7fff206f6fff  libsystem_info.dylib (542.40.4) <406353B2-E48A-3D20-B08F-0AB26ED8A0B3> /usr/lib/system/libsystem_info.dylib
    0x7fff206f7000 -     0x7fff20b94fff  com.apple.CoreFoundation (6.9 - 1778.105) <B4B8042A-9415-3F26-91AC-735C968B0D95> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff20b95000 -     0x7fff20dccfff  com.apple.LaunchServices (1122.45 - 1122.45) <42ED2E08-904B-3B62-B0B6-DACBE4988AAB> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
    0x7fff20dcd000 -     0x7fff20ea1fff  com.apple.gpusw.MetalTools (1.0 - 1) <72285C8A-5F98-31A0-9CA1-30CF4387584B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools
    0x7fff20ea2000 -     0x7fff210fefff  libBLAS.dylib (1336.140.1) <D4B16233-BAE7-3D63-BB59-5DCEC63345EB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
    0x7fff210ff000 -     0x7fff2114cfff  com.apple.Lexicon-framework (1.0 - 86.2) <09EC8AE4-7FC7-3D2D-A6DD-C484B664B1D5> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon
    0x7fff2114d000 -     0x7fff211bbfff  libSparse.dylib (106) <0FD77742-B7DB-3296-9D0F-0DEF7EB4FF7D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib
    0x7fff211bc000 -     0x7fff21239fff  com.apple.SystemConfiguration (1.20 - 1.20) <D59BEA1F-BD5D-383A-8977-64F5B72F16C4> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff2123a000 -     0x7fff2126efff  libCRFSuite.dylib (50) <2DADF4F9-0BD3-33CF-9939-979E69F2453C> /usr/lib/libCRFSuite.dylib
    0x7fff2126f000 -     0x7fff214a7fff  libmecabra.dylib (929.10) <58AA4922-A668-3165-802C-5FB4DF848E40> /usr/lib/libmecabra.dylib
    0x7fff214a8000 -     0x7fff21806fff  com.apple.Foundation (6.9 - 1778.105) <4F4709DD-C198-3AA1-86A0-71D2F2FDD65D> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff21807000 -     0x7fff218effff  com.apple.LanguageModeling (1.0 - 247.3) <EAAF99AF-2D5F-3EC5-B7F7-41D7236A09F3> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling
    0x7fff218f0000 -     0x7fff21a26fff  com.apple.CoreDisplay (237.4 - 237.4) <CDD47724-D213-3665-BD34-A51F374AE94F> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
    0x7fff21a27000 -     0x7fff21c97fff  com.apple.audio.AudioToolboxCore (1.0 - 1181.72.5) <541A108B-D52C-3F7B-B004-F31E16243BAF> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore
    0x7fff21c98000 -     0x7fff21e7dfff  com.apple.CoreText (677.6.0.4 - 677.6.0.4) <1E81E372-02B3-3E9C-BB48-33DC80E49158> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x7fff21e7e000 -     0x7fff2250ffff  com.apple.audio.CoreAudio (5.0 - 5.0) <A5ED9C97-E177-388F-AED8-D760C6963377> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x7fff22510000 -     0x7fff22867fff  com.apple.security (7.0 - 59754.141.1.702.3) <5A52B8E8-B1AF-3F29-AC97-5DBEE8C6A6AC> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff22868000 -     0x7fff22ac7fff  libicucore.A.dylib (66112.1) <9F2A881A-25DA-3386-9DCE-D2B67C2A4141> /usr/lib/libicucore.A.dylib
    0x7fff22ac8000 -     0x7fff22ad1fff  libsystem_darwin.dylib (1439.141.1) <75592BEC-777B-381F-8C07-15B8A4C712A7> /usr/lib/system/libsystem_darwin.dylib
    0x7fff22ad2000 -     0x7fff22dbdfff  com.apple.CoreServices.CarbonCore (1307.3 - 1307.3) <76566083-9F9C-3055-812A-079693A69D32> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
    0x7fff22dfd000 -     0x7fff22e37fff  com.apple.CSStore (1122.45 - 1122.45) <65919E05-BE7E-39AC-8768-B32E41E325C0> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore
    0x7fff22e38000 -     0x7fff22ee6fff  com.apple.framework.IOKit (2.0.2 - 1845.120.6) <A395F442-1253-3CA9-953F-7A235EEB7F67> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff22ee7000 -     0x7fff22ef2fff  libsystem_notify.dylib (279.40.4) <02E22D9D-01E2-361C-BB9A-B5BE18D28280> /usr/lib/system/libsystem_notify.dylib
    0x7fff22f41000 -     0x7fff23c8cfff  com.apple.AppKit (6.9 - 2022.70.111) <FA68A033-FD64-3F0B-8869-5C42CB9C6BE4> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff23c8d000 -     0x7fff23edbfff  com.apple.UIFoundation (1.0 - 729) <55B6D90D-A0ED-38D7-B858-1068A31C1C09> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
    0x7fff23edc000 -     0x7fff23eeefff  com.apple.UniformTypeIdentifiers (637 - 637) <CD0F9B05-DF9A-3961-AAF8-78A0A63C9BA9> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers
    0x7fff24359000 -     0x7fff249dffff  libnetwork.dylib (2288.140.9) <2DE517EE-E318-366B-A7FA-AD5F62D007CB> /usr/lib/libnetwork.dylib
    0x7fff249e0000 -     0x7fff24e7dfff  com.apple.CFNetwork (1240.0.4.5 - 1240.0.4.5) <83B8DEAA-82EE-36DD-ADF8-45E8A807BC21> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x7fff24e7e000 -     0x7fff24e8cfff  libsystem_networkextension.dylib (1295.140.4.701.1) <9C5A85AC-C593-34FD-8481-5CFC05DE3897> /usr/lib/system/libsystem_networkextension.dylib
    0x7fff24e8d000 -     0x7fff24e8dfff  libenergytrace.dylib (22.100.1) <EDE247D7-22AC-3339-AC3E-04A5BD13E3F2> /usr/lib/libenergytrace.dylib
    0x7fff24e8e000 -     0x7fff24eeafff  libMobileGestalt.dylib (978.140.1) <AC0BF1F3-5052-3FD8-808D-CBF55B3F7551> /usr/lib/libMobileGestalt.dylib
    0x7fff24eeb000 -     0x7fff24f01fff  libsystem_asl.dylib (385.0.2) <88F4051D-1CF5-314E-A952-247C38996E16> /usr/lib/system/libsystem_asl.dylib
    0x7fff24f02000 -     0x7fff24f1afff  com.apple.TCC (1.0 - 1) <898C8BE6-EBC0-3BEB-B898-2EF336802530> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x7fff24f1b000 -     0x7fff25280fff  com.apple.SkyLight (1.600.0 - 588.11) <370EFABF-8439-32C8-9136-0CB058CEE1A1> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
    0x7fff25281000 -     0x7fff2590afff  com.apple.CoreGraphics (2.0 - 1463.19.1) <C911B812-7401-3EAF-B365-A9B7B98B708A> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
    0x7fff2590b000 -     0x7fff25a02fff  com.apple.ColorSync (4.13.0 - 3473.8.1) <B66E5ABE-B72B-3607-8FB6-3CE54142829A> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync
    0x7fff25a03000 -     0x7fff25a5efff  com.apple.HIServices (1.22 - 716) <76A6ECCF-9098-3A1F-A80B-40408A9AA4A5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
    0x7fff25e05000 -     0x7fff26224fff  com.apple.CoreData (120 - 1048) <6D7D0B7E-7646-3F79-8108-0C1D11821749> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x7fff26225000 -     0x7fff2623afff  com.apple.ProtocolBuffer (1 - 285.24.10.20.1) <6EC4B8BC-C44A-3211-A0B5-A7298518231B> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer
    0x7fff2623b000 -     0x7fff263effff  libsqlite3.dylib (321.4) <2CBF5CD2-BECF-331B-904C-A88A54C6F6ED> /usr/lib/libsqlite3.dylib
    0x7fff2646d000 -     0x7fff26484fff  com.apple.commonutilities (8.0 - 900) <4D28711F-3425-31EB-A9D5-3FA489461EA3> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities
    0x7fff26485000 -     0x7fff26504fff  com.apple.BaseBoard (526 - 526) <8ABD1C28-584C-33E7-8BE8-4EFC5EEF1575> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard
    0x7fff26505000 -     0x7fff2654dfff  com.apple.RunningBoardServices (1.0 - 505.100.9) <BE0AEF0C-A31A-32F1-8157-9560A1A24633> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices
    0x7fff2654e000 -     0x7fff265c2fff  com.apple.AE (918.6 - 918.6) <677BFC57-B830-3090-9470-A21CB2A77C76> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
    0x7fff265c3000 -     0x7fff265c9fff  libdns_services.dylib (1310.140.1) <EABE9A6A-96DE-3A2E-B0E0-17F277A65757> /usr/lib/libdns_services.dylib
    0x7fff265ca000 -     0x7fff265d1fff  libsystem_symptoms.dylib (1431.140.1) <E9CB193F-260B-3835-B76E-A2209343FA1E> /usr/lib/system/libsystem_symptoms.dylib
    0x7fff265d2000 -     0x7fff2675dfff  com.apple.Network (1.0 - 1) <6A3C9CBC-DE8E-3D0A-BA52-316E70255DCD> /System/Library/Frameworks/Network.framework/Versions/A/Network
    0x7fff2675e000 -     0x7fff2678dfff  com.apple.analyticsd (1.0 - 1) <23CB7B45-967B-37B3-AF21-21B4885790CC> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics
    0x7fff2678e000 -     0x7fff26790fff  libDiagnosticMessagesClient.dylib (112) <8CE0D64A-597F-3048-80C3-590D866D067A> /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff26791000 -     0x7fff267ddfff  com.apple.spotlight.metadata.utilities (1.0 - 2150.30) <9B61E5D5-27C3-3282-A650-A2D15FA76FF7> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities
    0x7fff267de000 -     0x7fff26878fff  com.apple.Metadata (10.7.0 - 2150.30) <FEBC2256-7D84-3F2E-A770-A8665F62E20A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
    0x7fff26879000 -     0x7fff2687ffff  com.apple.DiskArbitration (2.7 - 2.7) <21325211-A5F7-3AB9-BDFE-6B6DC06E587E> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fff26880000 -     0x7fff26ee7fff  com.apple.vImage (8.1 - 544.6) <1DD123D7-ACC3-3FCB-838E-C91C6E4D31B8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
    0x7fff26ee8000 -     0x7fff271c5fff  com.apple.QuartzCore (1.11 - 927.24) <C2F144F0-B972-390B-B0DC-51B79F3B4DF2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x7fff271c6000 -     0x7fff27207fff  libFontRegistry.dylib (309.0.0.2) <D13D1774-9FC2-3A3B-BFD0-8ABFAF9AE1E0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x7fff27208000 -     0x7fff27348fff  com.apple.coreui (2.1 - 692.1) <0E2AE064-FD25-31B4-97EC-BA0AC0C16169> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x7fff27435000 -     0x7fff27440fff  com.apple.PerformanceAnalysis (1.278.3 - 278.3) <24DDF51B-8405-30AF-9879-5172C325BF0C> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
    0x7fff27441000 -     0x7fff27450fff  com.apple.OpenDirectory (11.7 - 230.40.1) <B7BB547E-B00F-37B3-A4A8-AF414F029E64> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x7fff27451000 -     0x7fff27470fff  com.apple.CFOpenDirectory (11.7 - 230.40.1) <E4682D99-DD7C-3C74-A0A1-E561B6E616C6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x7fff27471000 -     0x7fff2747dfff  com.apple.CoreServices.FSEvents (1290.120.6 - 1290.120.6) <78184C84-4633-3867-AACD-8F0256F40D5A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents
    0x7fff2747e000 -     0x7fff274a2fff  com.apple.coreservices.SharedFileList (144 - 144) <243CAB7D-EA1A-3322-9833-B4B24F63AB3E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList
    0x7fff274a3000 -     0x7fff274a5fff  libapp_launch_measurement.dylib (14.1) <2AE731D8-757E-3A23-8375-9D266B762CC3> /usr/lib/libapp_launch_measurement.dylib
    0x7fff274a6000 -     0x7fff274edfff  com.apple.CoreAutoLayout (1.0 - 21.10.1) <32846C89-8FED-3225-B370-34FB1DA82A85> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout
    0x7fff274ee000 -     0x7fff275d0fff  libxml2.2.dylib (34.26) <29CE75F5-D4D3-35BD-9B89-3B8970980C55> /usr/lib/libxml2.2.dylib
    0x7fff275d1000 -     0x7fff2761efff  com.apple.CoreVideo (1.8 - 0.0) <FE8A9F52-4140-36D8-BE09-800E75857EAD> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x7fff2761f000 -     0x7fff27621fff  com.apple.loginsupport (1.0 - 1) <FF0F8335-44A1-30C6-A005-5B50FAEC72CF> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport
    0x7fff285d9000 -     0x7fff285e9fff  libsystem_containermanager.dylib (318.100.4.700.1) <45445167-AFC7-3406-A858-9AE8D8F45907> /usr/lib/system/libsystem_containermanager.dylib
    0x7fff285ea000 -     0x7fff285fbfff  com.apple.IOSurface (290.8.2 - 290.8.2) <B98B7126-FFF8-343F-BE66-32212DE3BEBE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x7fff285fc000 -     0x7fff28605fff  com.apple.IOAccelerator (442.10 - 442.10) <19FBA808-F918-3BB2-BE78-A1B0D10D724D> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
    0x7fff28606000 -     0x7fff28729fff  com.apple.Metal (244.303 - 244.303) <A9397F90-E221-397B-BA10-B52135A72D68> /System/Library/Frameworks/Metal.framework/Versions/A/Metal
    0x7fff2872a000 -     0x7fff28746fff  com.apple.audio.caulk (1.0 - 70) <A8D1B95D-91AF-3FF5-9CD7-93661045C83A> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
    0x7fff28747000 -     0x7fff28831fff  com.apple.CoreMedia (1.0 - 2780.10.4.1.1) <237F9A0B-FE1F-3E4D-BE4D-8E27989EA845> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
    0x7fff28832000 -     0x7fff2898efff  libFontParser.dylib (305.6.0.6) <E2A105F9-8B39-3A45-94CE-6BF2DB31EB25> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib
    0x7fff2898f000 -     0x7fff28c8afff  com.apple.HIToolbox (2.1.1 - 1062) <621A473B-BE8A-3381-970A-25F253BE208A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
    0x7fff28c8b000 -     0x7fff28c9efff  com.apple.framework.DFRFoundation (1.0 - 267) <C10A9E83-76B8-35E7-9604-F29855DD76D8> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation
    0x7fff28c9f000 -     0x7fff28ca2fff  com.apple.dt.XCTTargetBootstrap (1.0 - 18119.2) <41D5117E-E262-3638-B01E-494487E7DB39> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap
    0x7fff28ca3000 -     0x7fff28cccfff  com.apple.CoreSVG (1.0 - 149) <6215F1BD-17B3-3B6E-8FB1-3C0AD5AD3C26> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG
    0x7fff28ccd000 -     0x7fff28f0afff  com.apple.ImageIO (3.3.0 - 2130.16.2) <15C8679A-DFE6-3664-977F-A82A97FD59C1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x7fff28f0b000 -     0x7fff29286fff  com.apple.CoreImage (16.3.0 - 1140.2) <3C2DE86C-89FA-3EC1-ACFE-6BE95F54B123> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
    0x7fff29287000 -     0x7fff292edfff  com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <02F2E0C6-0C0F-3390-A63B-189832967015> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore
    0x7fff292ee000 -     0x7fff292f1fff  libsystem_configuration.dylib (1109.140.1) <53B71513-3009-3A8C-A5AA-9C15DD0AB54E> /usr/lib/system/libsystem_configuration.dylib
    0x7fff292f2000 -     0x7fff292f6fff  libsystem_sandbox.dylib (1441.141.13.701.2) <1E19BC49-484C-32BB-8BB7-99D41C63F86E> /usr/lib/system/libsystem_sandbox.dylib
    0x7fff292f7000 -     0x7fff292f8fff  com.apple.AggregateDictionary (1.0 - 1) <CD5E6E8F-7AB6-345E-9243-D5D674DC0225> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary
    0x7fff292f9000 -     0x7fff292fcfff  com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <15CBB967-FAAE-3A22-A87F-4833A9D835E3> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo
    0x7fff292fd000 -     0x7fff292fefff  liblangid.dylib (136) <D6DDBEB6-7A9A-3F00-8DEF-18934CFC0A08> /usr/lib/liblangid.dylib
    0x7fff292ff000 -     0x7fff293a3fff  com.apple.CoreNLP (1.0 - 245.2) <F40C2289-9A6D-3C55-A6DA-FFAD41636415> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP
    0x7fff293a4000 -     0x7fff293aafff  com.apple.LinguisticData (1.0 - 399) <E6DC793D-3133-3D9B-BCF8-E4A628E45586> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData
    0x7fff293ab000 -     0x7fff29a53fff  libBNNS.dylib (288.100.5) <1E45AC70-6C75-3F27-9252-40DF6B2D674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib
    0x7fff29a54000 -     0x7fff29c26fff  libvDSP.dylib (760.100.3) <7F1276C0-C9F6-3C6F-A0F7-1EB4EA666BD8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
    0x7fff29c27000 -     0x7fff29c38fff  com.apple.CoreEmoji (1.0 - 128.4) <011AA15B-6988-3F36-81A3-2B52B561D6E0> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji
    0x7fff29c39000 -     0x7fff29c43fff  com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <28991DA2-1726-3F77-A9C5-4BB5AAEFA166> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer
    0x7fff29f3c000 -     0x7fff29f4cfff  com.apple.AssertionServices (1.0 - 505.100.9) <1B805E53-D42F-3019-88F0-64D3BD287DDB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices
    0x7fff29f4d000 -     0x7fff29fd8fff  com.apple.securityfoundation (6.0 - 55240.40.4) <D1E23625-27EF-37F4-93B8-E3162C1943BA> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
    0x7fff29fd9000 -     0x7fff29fe2fff  com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <8CF5B495-3026-3CE1-9EFC-8D7D71380A43> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement
    0x7fff29fe3000 -     0x7fff29fe7fff  com.apple.xpc.ServiceManagement (1.0 - 1) <D561E8B7-690C-3D18-A1E8-C4B01B8B9C11> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
    0x7fff29fe8000 -     0x7fff29feafff  libquarantine.dylib (119.40.4) <21C63859-6DFB-3463-9ADF-BB44FB28067C> /usr/lib/system/libquarantine.dylib
    0x7fff29feb000 -     0x7fff29ff6fff  libCheckFix.dylib (31) <1C2B822D-29D6-36E2-BBA3-F72DE49E038B> /usr/lib/libCheckFix.dylib
    0x7fff29ff7000 -     0x7fff2a00efff  libcoretls.dylib (169.100.1) <FC8265A0-9659-35D9-BA6F-6507A44742FE> /usr/lib/libcoretls.dylib
    0x7fff2a00f000 -     0x7fff2a01ffff  libbsm.0.dylib (68.40.1) <0CF67F8A-268D-320A-A3A4-D7C2D9AB8027> /usr/lib/libbsm.0.dylib
    0x7fff2a020000 -     0x7fff2a069fff  libmecab.dylib (929.10) <47A982DF-1436-366E-AC45-1DA068832AED> /usr/lib/libmecab.dylib
    0x7fff2a06a000 -     0x7fff2a06ffff  libgermantok.dylib (24) <189F508A-723B-345D-918F-178CF15077F3> /usr/lib/libgermantok.dylib
    0x7fff2a070000 -     0x7fff2a085fff  libLinearAlgebra.dylib (1336.140.1) <27358E5F-256F-309F-AAC8-BAC4A56C7BF4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
    0x7fff2a086000 -     0x7fff2a2a4fff  com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <B7F8218A-2DA2-35A4-9200-3BD52CCF125C> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork
    0x7fff2a2a5000 -     0x7fff2a2f4fff  com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <3993AC67-62B4-3E49-B5BF-E8F814CE6C97> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector
    0x7fff2a2f5000 -     0x7fff2a456fff  com.apple.MLCompute (1.0 - 1) <6026D664-0453-321F-81FE-A40AD902849E> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute
    0x7fff2a457000 -     0x7fff2a48dfff  com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <A194A321-8DD9-3051-97EC-3C4630946007> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix
    0x7fff2a48e000 -     0x7fff2a4e4fff  com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <A72429D4-3BED-34DD-BEDE-322A0975A8BC> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray
    0x7fff2a4e5000 -     0x7fff2a575fff  com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <0B333F06-FAD5-3689-9017-15334AD4F51C> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage
    0x7fff2a576000 -     0x7fff2a585fff  com.apple.AppleFSCompression (125 - 1.0) <1C5279EE-8F78-386E-9E4D-24A3785CACA2> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
    0x7fff2a586000 -     0x7fff2a592fff  libbz2.1.0.dylib (44) <6E82D414-3810-36CF-94FF-B1BDF48DB501> /usr/lib/libbz2.1.0.dylib
    0x7fff2a593000 -     0x7fff2a597fff  libsystem_coreservices.dylib (127.1) <6D84FA08-CB2B-34E1-9AB4-A54E82CB9161> /usr/lib/system/libsystem_coreservices.dylib
    0x7fff2a598000 -     0x7fff2a5c5fff  com.apple.CoreServices.OSServices (1122.45 - 1122.45) <097586DB-22C5-323A-BC5C-5AF75613846D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
    0x7fff2a794000 -     0x7fff2a7a6fff  libz.1.dylib (76.140.1) <A2FF8D14-1632-3047-9829-CC90239F97FF> /usr/lib/libz.1.dylib
    0x7fff2a7a7000 -     0x7fff2a7eefff  libsystem_m.dylib (3186.100.3) <1836B380-C579-3195-BC3F-77404D432186> /usr/lib/system/libsystem_m.dylib
    0x7fff2a7ef000 -     0x7fff2a7effff  libcharset.1.dylib (59) <3A46C22D-E678-356B-9BAD-6E837704D662> /usr/lib/libcharset.1.dylib
    0x7fff2a7f0000 -     0x7fff2a7f5fff  libmacho.dylib (980) <F7BDAFE5-4E49-39DD-8F94-CD5E49C91A90> /usr/lib/system/libmacho.dylib
    0x7fff2a7f6000 -     0x7fff2a811fff  libkxld.dylib (7195.141.49.702.12) <6585C769-FACC-3E47-844B-C7011292F3C5> /usr/lib/system/libkxld.dylib
    0x7fff2a812000 -     0x7fff2a81dfff  libcommonCrypto.dylib (60178.120.3) <B057F752-3057-394D-A3F6-AA11A04A6392> /usr/lib/system/libcommonCrypto.dylib
    0x7fff2a81e000 -     0x7fff2a828fff  libunwind.dylib (201) <9D6A6228-8DC3-3521-B458-4EDE4A9F5E65> /usr/lib/system/libunwind.dylib
    0x7fff2a829000 -     0x7fff2a830fff  liboah.dylib (203.58) <AC9E8A76-FCAA-3F97-802A-D22EF770463B> /usr/lib/liboah.dylib
    0x7fff2a831000 -     0x7fff2a83bfff  libcopyfile.dylib (173.40.2) <BD7EAE7B-28C1-36DF-96B8-F506D50DFF28> /usr/lib/system/libcopyfile.dylib
    0x7fff2a83c000 -     0x7fff2a843fff  libcompiler_rt.dylib (102.2) <BA910DC2-C697-3DAD-9A70-7C8CD5217AC3> /usr/lib/system/libcompiler_rt.dylib
    0x7fff2a844000 -     0x7fff2a846fff  libsystem_collections.dylib (1439.141.1) <21F2EF42-56ED-3E0F-9C29-94E0888DC52C> /usr/lib/system/libsystem_collections.dylib
    0x7fff2a847000 -     0x7fff2a849fff  libsystem_secinit.dylib (87.60.1) <E976428F-F9E2-334B-AA91-9AAD40234718> /usr/lib/system/libsystem_secinit.dylib
    0x7fff2a84a000 -     0x7fff2a84cfff  libremovefile.dylib (49.120.1) <5AC9F8EC-F0E8-3D8A-ADB5-96B5FB581896> /usr/lib/system/libremovefile.dylib
    0x7fff2a84d000 -     0x7fff2a84dfff  libkeymgr.dylib (31) <9FBE08F6-0679-3976-AFDC-1EAF40C3958F> /usr/lib/system/libkeymgr.dylib
    0x7fff2a84e000 -     0x7fff2a855fff  libsystem_dnssd.dylib (1310.140.1) <8C4D6C93-285F-3587-A986-5BB96A1C664F> /usr/lib/system/libsystem_dnssd.dylib
    0x7fff2a856000 -     0x7fff2a85bfff  libcache.dylib (83) <56DCEFF5-111E-32FD-B4E9-E148507C4FEC> /usr/lib/system/libcache.dylib
    0x7fff2a85c000 -     0x7fff2a85dfff  libSystem.B.dylib (1292.120.1) <A8E7368E-58FA-31E5-8D4D-FC2FED6100E6> /usr/lib/libSystem.B.dylib
    0x7fff2a85e000 -     0x7fff2a861fff  libfakelink.dylib (3) <6002BC93-3627-366E-8D21-A552D56CB215> /usr/lib/libfakelink.dylib
    0x7fff2a862000 -     0x7fff2a862fff  com.apple.SoftLinking (1.0 - 1) <3D0CEDFD-B263-39CA-8B31-E0A498D05EB3> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking
    0x7fff2a863000 -     0x7fff2a89afff  libpcap.A.dylib (98.100.3) <236EE73F-6D38-38E0-9BC0-B427DEB7F9FD> /usr/lib/libpcap.A.dylib
    0x7fff2a89b000 -     0x7fff2a98bfff  libiconv.2.dylib (59) <DEE0153A-BDF9-33CA-B8C7-3C39DB906B5E> /usr/lib/libiconv.2.dylib
    0x7fff2a98c000 -     0x7fff2a99dfff  libcmph.dylib (8) <83A69507-07D1-387F-9D06-1011E7909EAC> /usr/lib/libcmph.dylib
    0x7fff2a99e000 -     0x7fff2aa0ffff  libarchive.2.dylib (83.100.2) <45B577F5-0064-3E73-89B8-BE4A121B214F> /usr/lib/libarchive.2.dylib
    0x7fff2aa10000 -     0x7fff2aa77fff  com.apple.SearchKit (1.4.1 - 1.4.1) <7C264603-379D-38BF-A3EC-49C01059C5E5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
    0x7fff2aa78000 -     0x7fff2aa79fff  libThaiTokenizer.dylib (3) <BA265C01-176E-3F7D-97F6-7FAABB0CAEC8> /usr/lib/libThaiTokenizer.dylib
    0x7fff2aa7a000 -     0x7fff2aa9cfff  com.apple.applesauce (1.0 - 16.28) <EAFF4FEC-51F3-3D0D-9D99-E62E75937F1B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce
    0x7fff2aa9d000 -     0x7fff2aab4fff  libapple_nghttp2.dylib (1.41) <AC9520D7-D54F-3031-9503-FEA5A5ED5E56> /usr/lib/libapple_nghttp2.dylib
    0x7fff2aab5000 -     0x7fff2aacbfff  libSparseBLAS.dylib (1336.140.1) <7D926256-F187-33CA-87D6-74F1660C438A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib
    0x7fff2aacc000 -     0x7fff2aacdfff  com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <9BFE310E-E910-3228-BDF5-21A7C4468D89> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders
    0x7fff2aace000 -     0x7fff2aad3fff  libpam.2.dylib (28.40.1.700.1) <564320AF-69E5-3FEE-BE3A-E500B9B6786F> /usr/lib/libpam.2.dylib
    0x7fff2aad4000 -     0x7fff2aaf3fff  libcompression.dylib (96.120.1) <F36054C1-6074-3A22-82EF-6F4A2A52599C> /usr/lib/libcompression.dylib
    0x7fff2aaf4000 -     0x7fff2aaf9fff  libQuadrature.dylib (7) <256CB21E-2878-3F22-B4B5-E1FB60D64C9E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib
    0x7fff2aafa000 -     0x7fff2ae97fff  libLAPACK.dylib (1336.140.1) <02F2D4D1-8763-32D1-B5F9-9DD439EFC8E8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
    0x7fff2ae98000 -     0x7fff2aee7fff  com.apple.DictionaryServices (1.2 - 341) <FB843860-C7D5-3060-B50E-303A3CBAE9A9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
    0x7fff2aee8000 -     0x7fff2af00fff  liblzma.5.dylib (16) <455C9083-014D-3037-AC54-1395F3796734> /usr/lib/liblzma.5.dylib
    0x7fff2af01000 -     0x7fff2af02fff  libcoretls_cfhelpers.dylib (169.100.1) <6760D250-2628-3DA2-A8A4-6F438E09527A> /usr/lib/libcoretls_cfhelpers.dylib
    0x7fff2af03000 -     0x7fff2affefff  com.apple.APFS (1677.141.3 - 1677.141.3) <E4B0DF0F-E1A5-3FEF-A2A6-8105AD54D95A> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS
    0x7fff2afff000 -     0x7fff2b00dfff  libxar.1.dylib (452.140.1) <9E460111-1BBC-31FE-8CAF-FA8AEC22C1E9> /usr/lib/libxar.1.dylib
    0x7fff2b00e000 -     0x7fff2b011fff  libutil.dylib (58.40.3) <B5961283-0856-3D78-AE9C-EAFB6A903569> /usr/lib/libutil.dylib
    0x7fff2b012000 -     0x7fff2b03afff  libxslt.1.dylib (17.10) <52B300FD-B3F6-3689-9554-98B543A298C7> /usr/lib/libxslt.1.dylib
    0x7fff2b03b000 -     0x7fff2b045fff  libChineseTokenizer.dylib (37.1) <62BC78D3-1400-3366-A04E-C8BEE6AC00B5> /usr/lib/libChineseTokenizer.dylib
    0x7fff2b046000 -     0x7fff2b103fff  libvMisc.dylib (760.100.3) <560739C2-D16B-36CA-89F4-BD4DD2192333> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
    0x7fff2b104000 -     0x7fff2b19bfff  libate.dylib (3.0.6) <CCD85C79-E892-339A-B0AB-E385D4F635F5> /usr/lib/libate.dylib
    0x7fff2b19c000 -     0x7fff2b1a3fff  libIOReport.dylib (64.100.1) <0997845A-1FF3-35B3-A5ED-2FB16D07F624> /usr/lib/libIOReport.dylib
    0x7fff2b339000 -     0x7fff2b38cfff  com.apple.AppleVAFramework (6.1.3 - 6.1.3) <1D2A99E8-473C-3C56-BD50-98549FDC8932> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
    0x7fff2b38d000 -     0x7fff2b3a6fff  libexpat.1.dylib (26.141.1) <0416D6BA-2AEB-3BBA-8584-FA28E62E8007> /usr/lib/libexpat.1.dylib
    0x7fff2b3a7000 -     0x7fff2b3b0fff  libheimdal-asn1.dylib (597.140.4) <60E659ED-BF63-3853-868D-D82D981AA955> /usr/lib/libheimdal-asn1.dylib
    0x7fff2b3b1000 -     0x7fff2b3c5fff  com.apple.IconFoundation (479.4 - 479.4) <71915E97-2F3E-36EE-B000-0EE7B258DD29> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation
    0x7fff2b3c6000 -     0x7fff2b432fff  com.apple.IconServices (479.4 - 479.4) <C3E66299-D698-3AF5-B34D-D2782F91E106> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
    0x7fff2b433000 -     0x7fff2b4d1fff  com.apple.MediaExperience (1.0 - 1) <F5328457-1856-3DA3-B254-EC4FBBA7799F> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience
    0x7fff2b4d2000 -     0x7fff2b4fafff  com.apple.persistentconnection (1.0 - 1.0) <CF93C3EC-D1D1-3BAE-92B1-5D85A969F748> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection
    0x7fff2b4fb000 -     0x7fff2b509fff  com.apple.GraphVisualizer (1.0 - 100.1) <928039C0-8548-38A0-BBE9-6AA807CCE7B7> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer
    0x7fff2b50a000 -     0x7fff2b925fff  com.apple.vision.FaceCore (4.3.2 - 4.3.2) <13FFCD22-55DB-301B-9C6F-03C94266591B> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
    0x7fff2b926000 -     0x7fff2b96dfff  com.apple.OTSVG (1.0 - 677.6.0.4) <F89F3381-E8B0-3964-995E-6213AD6955B2> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG
    0x7fff2b96e000 -     0x7fff2b974fff  com.apple.xpc.AppServerSupport (1.0 - 2038.120.1.701.2) <C50E01B1-3B25-3237-A424-0E1FEBC3A890> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport
    0x7fff2b975000 -     0x7fff2b987fff  libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <24525668-9221-3A7B-8C64-CDAE418049DA> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib
    0x7fff2b988000 -     0x7fff2b98afff  libspindump.dylib (295.3) <E090FDF1-6C64-39B9-A750-63EC6AB7E0C1> /usr/lib/libspindump.dylib
    0x7fff2b98b000 -     0x7fff2ba4bfff  com.apple.Heimdal (4.0 - 2.0) <52976F1C-2F22-397A-8F21-38BEB3061DC2> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x7fff2bbeb000 -     0x7fff2bc27fff  com.apple.bom (14.0 - 235.3) <B849E4CE-F977-3F27-857C-8000AD4FE041> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x7fff2bc28000 -     0x7fff2bc71fff  com.apple.AppleJPEG (1.0 - 1) <2A8FF19B-B937-3F0B-A59B-A9A8B24F53E6> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG
    0x7fff2bc72000 -     0x7fff2bd51fff  libJP2.dylib (2130.16.2) <967ABC46-39E1-38CC-8BE5-FDE37AFB77BD> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x7fff2bd52000 -     0x7fff2bd55fff  com.apple.WatchdogClient.framework (1.0 - 98.120.2) <2907CD2F-A115-34CF-BB9D-DCFEBAEE78F3> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient
    0x7fff2bd56000 -     0x7fff2bd8cfff  com.apple.MultitouchSupport.framework (4440.3.1 - 4440.3.1) <9F19F332-ADC4-3D35-A9ED-C62AC334A704> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
    0x7fff2bd8d000 -     0x7fff2beebfff  com.apple.VideoToolbox (1.0 - 2780.10.4.1.1) <774F6519-3AF4-3B1C-BCA8-72B287B8CF05> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
    0x7fff2beec000 -     0x7fff2bf1ffff  libAudioToolboxUtility.dylib (1181.72.5) <F1E3759E-BE9B-30CE-97F0-669ECD0F012F> /usr/lib/libAudioToolboxUtility.dylib
    0x7fff2bf20000 -     0x7fff2bf40fff  libPng.dylib (2130.16.2) <BE17D73D-2A4F-3A46-85DE-A523D58A82F5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x7fff2bf41000 -     0x7fff2bfa2fff  libTIFF.dylib (2130.16.2) <48B3B58D-BC6F-3D7B-988C-729475BFACCA> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x7fff2bfa3000 -     0x7fff2bfbffff  com.apple.IOPresentment (58 - 37) <BA4B88DD-52FF-3F07-82E2-533E7D6548C0> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment
    0x7fff2bfc0000 -     0x7fff2bfc7fff  com.apple.GPUWrangler (6.3.6 - 6.3.6) <D41B27C4-9FC6-3F2F-8C65-06F9ED6EE43D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler
    0x7fff2bfc8000 -     0x7fff2bfcbfff  libRadiance.dylib (2130.16.2) <5B7B2CA5-D6ED-3A8E-97BC-A3D99EE023F9> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x7fff2bfcc000 -     0x7fff2bfd1fff  com.apple.DSExternalDisplay (3.1 - 380) <85C7B7A3-8E61-3773-A7A1-0E594C390144> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay
    0x7fff2bfd2000 -     0x7fff2bff6fff  libJPEG.dylib (2130.16.2) <164FF5FC-2979-394D-8474-D35A20394794> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x7fff2bff7000 -     0x7fff2c026fff  com.apple.ATSUI (1.0 - 1) <D64FE353-AFFA-3B55-8E85-F222434E2FC1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI
    0x7fff2c027000 -     0x7fff2c02bfff  libGIF.dylib (2130.16.2) <3EDEAB7F-7268-3DA5-898D-1C21579DC859> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x7fff2c02c000 -     0x7fff2c035fff  com.apple.CMCaptureCore (1.0 - 82.6) <E96DDCE5-8BCF-392D-84C6-87D76BC9DF9A> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore
    0x7fff2c036000 -     0x7fff2c07dfff  com.apple.print.framework.PrintCore (16.1 - 531.1) <D8F84239-11A0-311F-A66C-99C87F99D879> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
    0x7fff2c07e000 -     0x7fff2c14bfff  com.apple.TextureIO (3.10.9 - 3.10.9) <3AC1D19C-DACE-33A7-9C89-BDD3D38A7080> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO
    0x7fff2c14c000 -     0x7fff2c154fff  com.apple.InternationalSupport (1.0 - 61.1) <D4CAEFD9-602F-3112-AD33-A674F2A6EC7F> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport
    0x7fff2c155000 -     0x7fff2c1cffff  com.apple.datadetectorscore (8.0 - 674) <3B902938-2B3E-31A5-A57B-151BBB5D8BC8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
    0x7fff2c1d0000 -     0x7fff2c22dfff  com.apple.UserActivity (439 - 439) <59BC012A-4927-3FB9-9AEF-75F0096A1548> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity
    0x7fff2ce9b000 -     0x7fff2ceccfff  libSessionUtility.dylib (76.69) <9CA8B6AC-ADC8-3805-A7AE-2532B3C0EBB0> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib
    0x7fff2cecd000 -     0x7fff2d001fff  com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <99F6F2D8-189D-398C-A38C-B6B49F66A6E8> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x7fff2d002000 -     0x7fff2d067fff  com.apple.audio.AudioSession (1.0 - 76.69) <85C29DF5-2A9A-3029-8AF5-91E83074C414> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession
    0x7fff2d068000 -     0x7fff2d07afff  libAudioStatistics.dylib (27.64) <C46ED1DB-C7F4-3E56-B992-25821F9B1CE1> /usr/lib/libAudioStatistics.dylib
    0x7fff2d07b000 -     0x7fff2d08afff  com.apple.speech.synthesis.framework (9.0.66 - 9.0.66) <1746AB65-AAAA-3BAB-AAD3-C158FB532798> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x7fff2d08b000 -     0x7fff2d0f7fff  com.apple.ApplicationServices.ATS (377 - 516) <484D4858-74A8-3541-91E5-2C74F70A3824> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
    0x7fff2d0f8000 -     0x7fff2d110fff  libresolv.9.dylib (68.2) <78461752-674E-35D5-94D6-17E627802577> /usr/lib/libresolv.9.dylib
    0x7fff2d243000 -     0x7fff2d322fff  libSMC.dylib (20) <038349BC-2D55-3E20-B3C3-BFEEA36E730A> /usr/lib/libSMC.dylib
    0x7fff2d323000 -     0x7fff2d382fff  libcups.2.dylib (494.7) <0006C772-A113-37BC-A8AD-A7B96DE21EE2> /usr/lib/libcups.2.dylib
    0x7fff2d383000 -     0x7fff2d392fff  com.apple.LangAnalysis (1.7.0 - 254) <EEF814D5-A3F9-3FF4-8F1B-D6083AFAEC52> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
    0x7fff2d393000 -     0x7fff2d39dfff  com.apple.NetAuth (6.2 - 6.2) <2FB90509-3BD8-39CF-BE6A-5490F84FF284> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x7fff2d39e000 -     0x7fff2d3a5fff  com.apple.ColorSyncLegacy (4.13.0 - 1) <00861A68-F725-3E01-BDB9-64823636DD90> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy
    0x7fff2d3a6000 -     0x7fff2d3b1fff  com.apple.QD (4.0 - 416) <AAE33CA8-0995-3BA3-B5CE-4ED19706BB44> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
    0x7fff2d3b2000 -     0x7fff2da06fff  com.apple.audio.AudioResourceArbitration (1.0 - 1) <09E26A64-0C70-38AD-B9C9-7F8847E1F09F> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration
    0x7fff2da07000 -     0x7fff2da12fff  com.apple.perfdata (1.0 - 67.40.1) <4A3F192A-2416-3D16-B318-A160264359DE> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata
    0x7fff2da13000 -     0x7fff2da21fff  libperfcheck.dylib (41) <7D626792-9A87-3A1F-BE6E-C7D8FE62B800> /usr/lib/libperfcheck.dylib
    0x7fff2da22000 -     0x7fff2da31fff  com.apple.Kerberos (3.0 - 1) <69B24A09-0788-3ACA-A01C-358746980694> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff2da32000 -     0x7fff2da82fff  com.apple.GSS (4.0 - 2.0) <5C6BCBC8-F041-3588-AC99-94CD85737E2B> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x7fff2da83000 -     0x7fff2da93fff  com.apple.CommonAuth (4.0 - 2.0) <82E6D81F-8B40-3986-B5F2-CF151AD8C06C> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x7fff2dc64000 -     0x7fff2dc64fff  liblaunch.dylib (2038.120.1.701.2) <B79B00B1-954F-3EC4-9E22-A24E25CAE88D> /usr/lib/system/liblaunch.dylib
    0x7fff2fe93000 -     0x7fff2febafff  com.apple.RemoteViewServices (2.0 - 163) <960463A4-6F65-3E89-8918-FA77BF9F6ADC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
    0x7fff2febb000 -     0x7fff2fecafff  com.apple.SpeechRecognitionCore (6.1.25 - 6.1.25) <08338B73-5E68-33E3-93DC-F5BAF287CF82> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore
    0x7fff2fecb000 -     0x7fff2fed2fff  com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <927F7D7F-8BD2-3EF2-A239-C20010C2149E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
    0x7fff30100000 -     0x7fff30100fff  libsystem_product_info_filter.dylib (8.40.1) <BB06C92C-6BD7-310C-A176-DC0DCE8D9F2B> /usr/lib/system/libsystem_product_info_filter.dylib
    0x7fff301d8000 -     0x7fff301d8fff  com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <F46E0ACF-7524-3CA3-A64A-5DDF6081EB67> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
    0x7fff301fe000 -     0x7fff301fefff  com.apple.CoreServices (1122.45 - 1122.45) <05DA2462-9BFC-38D9-820A-8842710471D6> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff303ba000 -     0x7fff303bafff  com.apple.Accelerate (1.11 - Accelerate 1.11) <3D8DECC6-19B3-3A32-98CF-EB07536D1635> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x7fff33184000 -     0x7fff33187fff  com.apple.help (1.3.8 - 71) <745DA416-7B89-391F-9D7B-EBD78DB63056> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
    0x7fff333ed000 -     0x7fff333edfff  com.apple.ApplicationServices (48 - 50) <59E17F70-AB03-320D-B955-8F87F2C40898> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
    0x7fff33702000 -     0x7fff33702fff  libHeimdalProxy.dylib (79) <69042CA5-B0DE-392D-8B32-51446EA228C5> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib
    0x7fff36686000 -     0x7fff366a9fff  com.apple.openscripting (1.7 - 190.1) <D0430B21-C855-3DE4-A512-0708FC1CB9AE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
    0x7fff366aa000 -     0x7fff366adfff  com.apple.securityhi (9.0 - 55008) <4A0776E2-2CA9-3EFE-8653-1E96644D9B43> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
    0x7fff366ae000 -     0x7fff366b1fff  com.apple.ink.framework (10.15 - 227) <FDCF3900-B1C0-32E2-8C9B-C8E6D43B1374> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
    0x7fff366b2000 -     0x7fff366b5fff  com.apple.CommonPanels (1.2.6 - 101) <5A909E1B-3060-3C41-8B93-EB2CAD9BAA61> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
    0x7fff366b6000 -     0x7fff366bdfff  com.apple.ImageCapture (1711.5.2.1 - 1711.5.2.1) <321754DF-D200-39D3-A184-FF13D4802A70> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
    0x7fff3cc12000 -     0x7fff3cc15fff  com.apple.print.framework.Print (15 - 271) <C3581434-D285-320A-977F-77070BFC5F3B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
    0x7fff3cc16000 -     0x7fff3cc19fff  com.apple.Carbon (160 - 164) <C916A7BB-B2B4-3248-B3EA-5A59C066D68B> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff3cecc000 -     0x7fff3ceebfff  com.apple.private.SystemPolicy (1.0 - 1) <89781097-BA30-3186-B368-3830D1FE4FC0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy
    0x7fff3d829000 -     0x7fff3d83bfff  libmis.dylib (274.140.2) <D8990A31-A5AE-3535-BE5E-3EE9A8D0C9F9> /usr/lib/libmis.dylib
    0x7fff6bb8b000 -     0x7fff6bb91fff  libCoreFSCache.dylib (200.12) <B6360761-3B05-35AE-8E0C-F819414FD093> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
    0x7fff6bb92000 -     0x7fff6bb96fff  libCoreVMClient.dylib (200.12) <4D617E02-85B8-3BC2-82FE-5CEA77809181> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
    0x7fff6bb97000 -     0x7fff6bba6fff  com.apple.opengl (18.5.9 - 18.5.9) <610E765C-8C0D-3422-AD6E-636D3EBD2AD0> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x7fff6bba7000 -     0x7fff6bba9fff  libCVMSPluginSupport.dylib (18.5.9) <C7B33518-2685-3985-ABCB-FC3B0105748C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
    0x7fff6bbaa000 -     0x7fff6bbb2fff  libGFXShared.dylib (18.5.9) <AD53ED9A-C694-3EF4-863E-898E88F6D84C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
    0x7fff6bbb3000 -     0x7fff6bbe6fff  libGLImage.dylib (18.5.9) <6C478ED9-E513-3E43-B9F1-D15A20A0EE85> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
    0x7fff6bbe7000 -     0x7fff6bc23fff  libGLU.dylib (18.5.9) <D5473328-FD13-36A5-9CAC-CF4F59CDAA29> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x7fff6bdb8000 -     0x7fff6bdc2fff  libGL.dylib (18.5.9) <08A0476A-D04F-3816-AA4D-11EC2467F748> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x7fff6d202000 -     0x7fff6d25afff  com.apple.opencl (4.6 - 4.6) <8C87D26C-12C6-33E8-AE32-45B699667DB3> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x7fff6e304000 -     0x7fff6e30bfff  com.apple.agl (3.3.4 - AGL-3.3.3) <BE049FFB-FE46-3811-9A6C-688FA6BBC557> /System/Library/Frameworks/AGL.framework/Versions/A/AGL

Process:               WinBox [6138]
Path:                  /Applications/WinBox.app/Contents/MacOS/WinBox
Identifier:            my.example.com
Version:               0.1 (0.1)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2024-12-02 16:58:49.0691 -0300
OS Version:            macOS 11.7.10 (20G1427)
Report Version:        12
Anonymous UUID:        D4F5F1A5-CE7B-4212-958F-4C0F4EF6E079


Time Awake Since Boot: 11000 seconds

System Integrity Protection: enabled

Notes:
Failed to extract dyld error info: The size of the data is not what is expected

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace DYLD, Code 4 Symbol missing
Symbol not found: _kIOMainPortDefault
Referenced from: /Applications/WinBox.app/Contents/MacOS/WinBox
Expected in: /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
in /Applications/WinBox.app/Contents/MacOS/WinBox

Application Specific Information:



Error Formulating Crash Report:Failed to extract dyld error info: The size of the data is not what is expected

Thread 0 Crashed:
0   dyld                          	       0x113071e0a __abort_with_payload + 10
1   dyld                          	       0x11309abb1 abort_with_payload_wrapper_internal + 80
2   dyld                          	       0x11309abe3 abort_with_payload + 9
3   dyld                          	       0x11301a412 dyld::halt(char const*) + 672
4   dyld                          	       0x11301e383 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 9932
5   dyld                          	       0x113016224 dyldbootstrap::start(dyld3::MachOLoaded const*, int, char const**, dyld3::MachOLoaded const*, unsigned long*) + 450
6   dyld                          	       0x113016025 _dyld_start + 37


Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000002000209  rbx: 0x0000000000000000  rcx: 0x00007ffee7f79ec8  rdx: 0x00007ffee7f7a330
  rdi: 0x0000000000000006  rsi: 0x0000000000000004  rbp: 0x00007ffee7f79f10  rsp: 0x00007ffee7f79ec8
   r8: 0x00007ffee7f79f30   r9: 0x0000000000000000  r10: 0x0000000000000093  r11: 0x0000000000000246
  r12: 0x0000000000000093  r13: 0x00007ffee7f7a330  r14: 0x0000000000000004  r15: 0x0000000000000006
  rip: 0x0000000113071e0a  rfl: 0x0000000000000246  cr2: 0x00000001130a5682
  
Logical CPU:     0
Error Code:      0x02000209 
Trap Number:     133


Binary Images:
       0x113015000 -        0x1130b0fff dyld (*) <bd607394-9008-33b9-b98b-a5886668e52c> /usr/lib/dyld

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=713.0M resident=0K(0%) swapped_out_or_unallocated=713.0M(100%)
Writable regions: Total=8568K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8568K(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
STACK GUARD                       56.0M        1 
Stack                             8192K        1 
VM_ALLOCATE                          8K        2 
__DATA                            11.0M      255 
__DATA_CONST                      12.4M      149 
__DATA_DIRTY                       504K       87 
__FONT_DATA                          4K        1 
__LINKEDIT                       501.8M        5 
__OBJC_RO                         70.3M        1 
__OBJC_RW                         2496K        1 
__TEXT                           211.2M      260 
__UNICODE                          588K        1 
===========                     =======  ======= 
TOTAL                            874.2M      764

Tue Dec 03, 2024 12:11 am

Isn't it related?

*) bump minimal macOS version to 12.0, because 11.0 is EOL and dropped by Qt

DancingElbowGrease · Tue Dec 03, 2024 2:35 am

+1 for
"Many UI buttons need Hover help text"

Not only buttons.
All those abbreviations like "R" for running, "D" for dynamic and so on.
I'm new to MT so I have to keep using the old WinBox trying to figure out what all those mean.

Input fields could pop-up some hints on hover as well.
That'd reduce the need to dive into documentation as often.

jimmer · Tue Dec 03, 2024 12:24 pm

I've noticed a bit of a cosmetic bug, when copying from one partition to another the partition list does not update immediately like it does with v 3.41, still shows the pre-copy version in the window as if the copy process did not trigger a refresh.

Nothing terrible, just something ive noticed in the last few beta's

Should note this is on the Linux version of Winbox 4 beta, tested with Winbox 4beta13 and 3.41 was running under Linux using wine

minelli · Tue Dec 03, 2024 12:52 pm

Isn't it related?
*) bump minimal macOS version to 12.0, because 11.0 is EOL and dropped by Qt

I hadn't noticed that, but in any case, the Winbox 4b12 version isn't opening and is generating errors, and according to the changelog it should run on macOS BigSur.

It's a shame that they discontinued macOS 11, because in some countries a new MacBook isn't that cheap.

ryandard · Tue Dec 03, 2024 4:28 pm

please bring back address hover like winbox 3, it's very usefull

mszru · Tue Dec 03, 2024 6:35 pm

Quick search and windows list are great new features!

The quick search however requires some fine tuning. WinBox opens a new window if it hasn't been opened before or brings the existing window to the front. And from my point of view that is logical and expected. If I have 2 instances of the same window (with different tabs selected) open then the WinBox does not switch to the window with active tab that I am searching for, but switches the tab of the foreground window.

This is an example of such behavior:

Step 1: open Firewall window, switch to Connections tab and then spawn another Firewall window with active Address Lists tab.

Search1.png

Step 2: in the Quick search type in "Connections" and select "IP > Firewall > Connections" from the results.

Search2.png

Step 3: instead of bringing the window with active Connections tab to the front WinBox switched active tab in the other window.

Search3.png

infabo · Tue Dec 03, 2024 7:24 pm

Isn't it related?

I hadn't noticed that, but in any case, the Winbox 4b12 version isn't opening and is generating errors, and according to the changelog it should run on macOS BigSur.

It's a shame that they discontinued macOS 11, because in some countries a new MacBook isn't that cheap.

beta12 does not run on BigSur. It was already broken.

dang21000 · Tue Dec 03, 2024 11:04 pm

After few hours of use this b12 to manage multiples devices at the same time on a laptop (14p full hd), the right-bar lost lot of display content/space compared to 3.4x. And its worst when comparing two dev by puting 2 winbox side2side.

And if toggling theses 2 winbox up/down mode, its hard with long list (but usable)... and this time, it's the main left menu that is not fully displayed and stay cropped on the lower part..

rexsllemel · Wed Dec 04, 2024 1:28 pm

I have problem here, I can't use now the winbox4. The app can open no problem but since I change my monitor and location, the winbox4 app was out of window and I don't know how to reset it. I already deleted the app and asset, redownload but it still out of windows.

Screenshot 2024-12-04 192503.png

Edit:
If the app is opening off-screen, select the application on the taskbar and press this combination to move the window to your current monitor: Windows + Shift + Arrow Keys (Left or Right).

source:
https://answers.microsoft.com/en-us/win ... 48a143808f

Wed Dec 04, 2024 3:31 pm

Isn't it related?

I hadn't noticed that, but in any case, the Winbox 4b12 version isn't opening and is generating errors, and according to the changelog it should run on macOS BigSur.

It's a shame that they discontinued macOS 11, because in some countries a new MacBook isn't that cheap.

you can upgrade nearly any macbook to macOS 12. follow guide here: https://dortania.github.io/OpenCore-Leg ... -installer

karlisi · Wed Dec 04, 2024 4:05 pm

I have problem here, I can't use now the winbox4. The app can open no problem but since I change my monitor and location, the winbox4 app was out of window and I don't know how to reset it.

Thanks for your solution. Winbox4, if opened on second monitor stays there even if that monitor is removed, unlike other apps. As result you can't use it.

dredex · Thu Dec 05, 2024 9:46 am

I can't change Switch>VLAN settings on CRS112. VLAN window is empty, with old WinBox it works just fine.

infabo · Thu Dec 05, 2024 12:08 pm

I hadn't noticed that, but in any case, the Winbox 4b12 version isn't opening and is generating errors, and according to the changelog it should run on macOS BigSur.

It's a shame that they discontinued macOS 11, because in some countries a new MacBook isn't that cheap.
you can upgrade nearly any macbook to macOS 12. follow guide here: https://dortania.github.io/OpenCore-Leg ... -installer

This is not something everybody wants to do. It is like posting a tutorial to install LineageOS on your Android phone.

pe1chl · Thu Dec 05, 2024 3:09 pm

On the other hand, it is not really MikroTik's task to work around the release and support cycle of other equipment... or the fact that people don't have money to renew the equipment they earlier have bought.

infabo · Thu Dec 05, 2024 6:04 pm

Please introduce the possibility to disable workspace "auto-save". Why even auto-save is a feature at all? There is a "Save" button in the workspace drop-down list. Is the button there just for the sake of layout needs a button?

I use a tiling window manager and I **hate** it when all properly - painfully in mouse drag-drop as winbox4 still has no proper window layouting built-in - aligned windows appear overlapping and Winbox4 auto-saves this state which I can't undo. Please, I wish for Xmas.

teslasystems · Fri Dec 06, 2024 1:23 am

What's new in v4.0beta13:
*) move form tab's icon to left side to not overlap with scrollbar

What is it? If you mean that the group collapse/expand arrow was moved to the left, it doesn't solve the visual issue. A scrollbar overlaps with horizontal lines anyway. Same with scrollbar on the very right side, it overlaps with "Anchor" buttons. And everything has the same color... It looks awful.
.

Scrollbars.png

Edified · Fri Dec 06, 2024 6:39 pm

I ran into a long list and tried was frustrated that I couldn't use Page Down, Page Up, Home & End. Please add to the know issues list (beta13 on Win11 & MacOS15).

Additionally the Scroll Bar width should be static (no animated hit targets) and ideally the standard width.

Importantly, the Scroll Bar click in margin behavior doesn't match the OS behavior of scroll a page at a time; Instead it jumps to position, which makes it impossible to scroll a page at a time for long lists. Please add to known issues

AdminioBanderas · Fri Dec 06, 2024 8:38 pm

I can't find it or maybe this feature hasn't been implemented yet.
In version 3 there was an option to save all connections under a master password. Is this in the new version?

Paternot · Fri Dec 06, 2024 9:15 pm

A cosmetic request:

Could we have an SVG icon for the Winbox? The beta comes with one png icon, and due to my screen resolution it gets kinda ugly. And SVG icon would solve it for Linux users (o/), and (I think) MacOS ones. No idea if would be of any use to Windows users.

Pretty please? With a cherry on top?

pacmanfan · Sat Dec 07, 2024 6:37 am

v4 on Windows 11 is quite slow with large lists compared to v3. I have a router with over 1000 leases under DHCP Server, and over 2500 IP ARP entries--it is quite laggy to scroll around and interact with the list items. It seems to be CPU-limited, maxing out one core whenever I have a large list open.

TikApp on iOS is essentially unusable on the DHCP Server Leases section on my router with over 1000 leases; it literally takes minutes to load the list.

optio · Sat Dec 07, 2024 11:30 am

Could we have an SVG icon for the Winbox? The beta comes with one png icon, and due to my screen resolution it gets kinda ugly. And SVG icon would solve it for Linux users (o/), and (I think) MacOS ones.

Unfortunately MacOS doesn't support SVG for app icons, but it supports multiple app icon PNG images with different resolution in icons resource file (.icns) which would be loaded for best fit depending on screen DPI and usage, different icon image is used for different presentation views (icon in app notification, different icons in Finder for column listing or gallery preview view type...). Currently Winbox has single icon image for MacOS app which is not optimal and also bit blurry in some cases, for eg. when hitting space in Finder on app.

Paternot · Sat Dec 07, 2024 1:08 pm

Unfortunately MacOS doesn't support SVG for app icons, but it supports multiple app icon PNG images with different resolution in icons resource file (.icns) which would be loaded for best fit...

Really? I could swear they used SVG too. Yes, we can have several icons, one for each resolution. I just thought MacOS used SVG, and so they could provide it for Linux and Mac users. And yes, we have a single icon on the Linux version too. Several sizes would solve the problem alright.

optio · Sat Dec 07, 2024 1:18 pm

https://en.wikipedia.org/wiki/Apple_Icon_Image_format

Windows ICO file also supports multiple resolutions for icons, for Linux single SVG icon file should be enough because it is supported by common desktop environments.
There is no universal icon file type to be used for any OS.

Paternot · Sat Dec 07, 2024 3:45 pm

There is no universal icon file type to be used for any OS.

Really, they should all use SVG. Open, easy, and 100% scalable. Well, ok: PNG too, if someone wants to put a picture there. But SVG would be great...

optio · Sat Dec 07, 2024 4:39 pm

I meant currently, but yes, more standards more life is easier.

Amm0 · Sat Dec 07, 2024 5:37 pm

I think it's Linux where the SVG is useful. On Mac/Windows, the icon file isn't needed since it bundled.

But with Linux, there are different window managers. And using a SVG allow you use the "scalable" icon directory, while rastered PNG/etc require using the resolution specific directories with different WM using subtly different resolutions. Basically an SVG be easier for anyone packaging winbox or setting the icon manual since the "scalable" icon directory is now pretty standardized.

Another solution is various winbox icons formats should be included on https://mikrotik.com/logo site, which has a lot of detail, but not the winbox icon.

nagaju · Sun Dec 08, 2024 5:36 pm

+1 for native Windows ARM64. Running on Win Surface 11

syadnom · Sun Dec 08, 2024 7:59 pm

4.0beta13 is looking really good

PLEASE fix the keyboard issue when hitting numberkey enter blanking the link and not executing. ie, please make both keyboard enter keys behave the same.

also, there's some mouse wheel accelleration that doesn't match the system (macos) so I am not really able to scroll through long lists, it basically zooms top to bottom, forcing the use of the scroll bar (which is tiny)

lilianmoraru · Mon Dec 09, 2024 1:27 pm

Beautiful. Finally a Quick Search/Jump To feature, just like the phone app. The Windows management is also much better now - maybe needs a "minimize" feature now.

Screenshot 2024-12-09 at 13.23.42.png

dang21000 · Mon Dec 09, 2024 9:37 pm

And logs are still unreadable due to the online format

Why theme don't simple use the OS default interface ...? like all apps

Tue Dec 10, 2024 10:10 am

What is "online format", not clear what you mean about logs

Tue Dec 10, 2024 10:13 am

What's new in v4.0beta14:


*) add autoscroll feature for windows like Log/Ping/Traceroute/etc. 
*) improve left menu popup usability 
*) allow multi item drag and drop
*) add support for table scrolling when dragging items with mouse
*) add support for moving files in Files window to other dirs
*) show system note at login if configured
*) clicking on zoom value label will reset zoom to 100%
*) show filtered rows count if filter applied
*) show status fields in ping and torch windows
*) implement support for directory upload
*) improve max upload speed
*) allow copying Resource bottom panel text field values
*) auto close Terminal window if disconnected with Ctrl+D
*) fix ctrl+wheel zooming in popups/overlays
*) do not show empy context menu elemenets in System Packages
*) wrap ALL one-line text input fields to new line when width reached
*) calculate minimal form's width including "not" and "optional" buttons
*) fix multiline comment header size in table panel
*) allow backspace to close optional fields (empty text field + backspace)
*) add context menu also for MultiLine text input (Copy/Paste/Select All)
*) fix some complex column value updating (DHCP Server/Lease/Bridge Port)
*) fix sunion+single field when unsetting field (DNS/Static/Forward-To)
*) fix show correct selected rows count (when using shift + click)
*) check if window/view exists before restoring from workspace
*) improve ordered table load performance when sorted by #
*) improve table load performance

mozerd · Tue Dec 10, 2024 11:20 am

Winbox v4.0beta14
Win11 23H2 (OS Build 22632, 4541)

It took 4 attempts to install this version ... at each attempt the progress showed to completion then closed with no restart. After 4th attempt manuel restart opened Winbox 4

Tue Dec 10, 2024 11:26 am

Same problem here.

WIN 11 23H2 22631.4460

Tue Dec 10, 2024 11:30 am

Installed.

Still no vertical column dividers.
Shift+ArrowKeys or MouseClick+Shfit+MouseClick should let check/uncheck consecutive rows.

Edit: after restart Mouse+Shift seems to work but "real admins use real keyboards"

Tue Dec 10, 2024 11:39 am

Same problem here.

WIN 11 23H2 22631.4460

After 3th attempt, it succeeded and restarted with new version.

nmt1900 · Tue Dec 10, 2024 12:44 pm

Can we please get something done with this awful waste of space in "non-inline" comments?
We do have inefficient space use everywhere but "non-inline" comments look like worst example of this. This is almost tolerable everywhere else, but these comment lines are the ultimate abomination, which makes this setting unusable while I use it all the time in WinBox 3 - this screenshot should be self-explanatory why it cannot be used in a same way in WinBox 4.

snap 2024-12-09 at 10.34.29.png

teslasystems · Tue Dec 10, 2024 1:19 pm

Much better!

Still waiting for:
1. Gridlines in tables
2. Always visible column header dividers (not only when a mouse cursor is over a header).
3. Coloring in logs.
4. Constant character width font.

Also noticed that the memory usage string on resources panel may be clipped sometimes.
.

MemUsage.png

Or like that, if you click on it.
.

MemUsage2.png

jamrobe · Tue Dec 10, 2024 1:49 pm

I've been using the new version of winbox quite a bit recently and i must applaud your redesign, as it really feels much nicer to use.

But there are a few small tweaks i'd love to see implemented:
1. A button in the system/clock tab to be able to sync the router's clock with the client's clock. This would be really useful for routers with no access to the internet. And just being able to quickly take a router from 1970 to current year with just a single button would make everything much simpler.
2. The id column on tables be made a bit larger since on all three of my linux machines starting from the 10th entry the numbers just get clipped to ... forcing me to extend the column manually.

3. Some improvements to the Packet sniffer ux. If the packet sniffer is running and i accidentally apply changes to the filters i get an error and the filters get reset, the latter of which i really don't feel is necessary. This is annoying since most of the time i'd have to then stop the sniffer and rewrite all the changes.
Another thing that happens quite often, mostly due to the first problem mentioned, is that i forget to apply changes after i made them, so a bit of ui telling you there's unsaved changes would go quite a long way in my opinion.
And as a last sniffer quirk, there is no way, from what i can see, to export the currently saved packets as a .pcap from the ui, forcing me to do that from the terminal, which i feel is a bit odd.

Sincerely hope you'll take my opinions into consideration and keep up the good work!
- Jamrobe

gigabyte091 · Tue Dec 10, 2024 3:14 pm

Same problem here.

WIN 11 23H2 22631.4460

Same here, after third attempt winbox was installed, W11Pro 23H2 build: 22631.4460

maisondasilva · Tue Dec 10, 2024 4:40 pm

When accessing a hap lite and downloading and installing it, before finishing the download, winbox closes by itself!

Source
WinBox.exe

Summary
Stopped working

Date
‎10/‎12/‎2024 11:36

Status
Report sent

Description
Faulting Application Path: C:\Users\Maison\OneDrive\Backup Mikrotik\WinBox.exe

Problem Signature
Problem Event Name: APPCRASH
Application Name: WinBox.exe
Application Version: 0.0.0.0
Application Timestamp: 6752e640
Faulting Module Name: WinBox.exe
Faulting Module Version: 0.0.0.0
Faulting Module Timestamp: 6752e640
Exception Code: c0000005
Exception Offset: 0000000000cfe9d2
Operating System Version: 10.0.26120.2.0.0.256.48
Locale ID: 1046
Additional Information 1: 53d2
Additional Information 2: 53d2161220e6a61b95f3b0caa9f0f9ce
Additional Information 3: d957
Additional Information 4: d957a2c3575d42b9c2216b4d9014e163

Additional Problem Information
Memory Slot ID: a731814cecb9447b91fb55cd9628225f (1295723659275018847)

connectthedots · Tue Dec 10, 2024 4:52 pm

Anyone else experiencing "word wrapping" in the password field?
I am using the latest beta for Linux.
When I select the device from the saved list, the password field now shows multiple lines.

Screenshot_20241210_074934.png

stmx38 · Tue Dec 10, 2024 6:00 pm

Anyone else experiencing "word wrapping" in the password field?

Same on macOS.

arturro · Tue Dec 10, 2024 10:28 pm

Hi, I have just found notice in first post that currently it is not possible to change order of columns by dragging them, but is there any other option to achieve such functionality?

syadnom · Tue Dec 10, 2024 11:53 pm

Hi, I have just found notice in first post that currently it is not possible to change order of columns by dragging them, but is there any other option to achieve such functionality?

it would be really nice to get this back. I used it a lot.

MTNick · Wed Dec 11, 2024 3:32 am

MacBook Air M3
Mac Mini M4 Desktop
Both on MacOS Sequoia 15.1.1

Update went well for both devices this morning. Both do have the login screen password word wrapping.

Thanks for all the fixes

teslasystems · Wed Dec 11, 2024 12:02 pm

Anyone else experiencing "word wrapping" in the password field?

Yes, same on Windows. Not sure, if it's good or bad...
And it's not only in password field, every field has such behavior.

Wed Dec 11, 2024 1:48 pm

Yes, that was an intentional change, not a bug:

*) wrap ALL one-line text input fields to new line when width reached

lilianmoraru · Wed Dec 11, 2024 2:05 pm

This bug is still present on Linux(and I think it was on macOS as well but not sure), WinBox 4.0beta14 ("Loading address db failed:"):

Screenshot from 2024-12-11 13-57-12.png

Conditions:
* Linux
* Happens at every WinBox startup, when there are no "Saved" connections. Saving a single connection and then removing it, solves the problem - that means, the code should just make sure the DB is created, instead of throwing this error.

rplatt · Wed Dec 11, 2024 2:38 pm

CTRL-A isn't working in files window in 4.14

za7 · Wed Dec 11, 2024 8:40 pm

"ERR: Could not connect. MacConnection syn timeout"

Occurs when the router is set to no default configuration on both Windows WinBox 4 and Linux WinBox4 when trying login using mac address.
Had to use WinBox 3.41 on Windows to setup devices.

stmx38 · Wed Dec 11, 2024 9:44 pm

This bug is still present on Linux(and I think it was on macOS as well but not sure), WinBox 4.0beta14 ("Loading address db failed:"):

Same was and still on macOS.

nmt1900 · Fri Dec 13, 2024 12:14 pm

Yes, that was an intentional change, not a bug:

*) wrap ALL one-line text input fields to new line when width reached

That is a side-effect of vertical split (vs horizontal split on Winbox 3) in start window. Vertical split in start window makes address list view usability worse - and it will be even worse than now when we finally be able to get "RoMON agent" and "Note" fields back to address list view.

Fri Dec 13, 2024 12:54 pm

That has no relation at all.

ToTheFull · Fri Dec 13, 2024 1:03 pm

I still have no warning colours in my logs, exmaple blue/red, is this still on the list. Dark mode is what I'm using.

Fri Dec 13, 2024 1:04 pm

Yes, it's a known missing feature, these things are coming. WinBox4 is still in beta, and has not reached feature parity with old version.

ToTheFull · Fri Dec 13, 2024 1:11 pm

Yes, it's a known missing feature, these things are coming. WinBox4 is still in beta, and has not reached feature parity with old version.

Ok thanks

nmt1900 · Fri Dec 13, 2024 2:39 pm

That has no relation at all.

By "side-effect" I meant that vertical split causes password field to be much shorter/narrower than it is in Winbox 3.

Fri Dec 13, 2024 3:19 pm

That's just not true. Open winbox and you will see there is plenty of space for longer password field. It can be easily two times longer, there is space for that

atomicduck · Fri Dec 13, 2024 4:41 pm

I am setting up a LAN in a warehouse - worked on 60 devices over the last two weeks and tried using the new WinBox. The program is a piece of c*ap. It’s slow to start, unnecessarily large, and the interface is an abomination. I absolutely hate it. Starting it on a slow VM takes about 10–15 seconds, while the old one starts immediately.

The screen efficiency is terrible. I often need 3–4 connections to multiple devices on the same 14" screen during testing and monitoring. Even on a large 27" screen, the new WinBox is a mess. It’s almost impossible to manage several devices at once on the same screen. Just the login interface alone takes up more than 30% of the screen.

The horizontal tabbed design is terrible because you can’t easily scroll side to side, while vertical scrolling is far more practical. The menu system is practically unusable. What if I’m using an 11" laptop on top of a crane while fixing something? I rely on WinBox to visualize and monitor data effectively. The terminal is nowhere near a replacement for that, nor should it be. The new WinBox looks like you’re deliberately trying to discourage users from using it.

To illustrate how bad the new design is: with the new WinBox, I can fit exactly 27 CAPs on my screen. With the old WinBox, I can fit exactly 44 on the same work laptop. And what did you do? Introduced alternating row colors. Believe it or not, the old table model was better. There is no vertical separation now, and for condensed data that is a must.

A network with 50 APs typically has about 300–400 APs and virtual APs. Do you honestly think we benefit from seeing less information on the screen when trying to check channels? What about a larger LAN with 100 APs and 4 SSIDs per frequency? That’s 800 APs. How are we supposed to manage that effectively?

The same problem exists everywhere I look in the new WinBox: slower, more cumbersome, less practical, and more screen space wasted on making things look “pretty.” You’ve done a bad job and keep doubling down on it. This reminds me of the new Jaguar campaign. Let me tell you directly: if you force me to use this coloring-book interface by making the old version obsolete, I’ll move to Cambium and be done with it. Their interface is already bad, but at least their operations are more streamlined, and project prices are more or less the same for entry level devices.

Paternot · Fri Dec 13, 2024 6:19 pm

To illustrate how bad the new design is: with the new WinBox, I can fit exactly 27 CAPs on my screen. With the old WinBox, I can fit exactly 44 on the same work laptop. And what did you do? Introduced alternating row colors. Believe it or not, the old table model was better. There is no vertical separation now, and for condensed data that is a must.

Have You tried to zoom out the screen? It's "Ctrl + mouse wheel". Works wonders to increase interface density.

atomicduck · Fri Dec 13, 2024 8:30 pm

Yes, and it is still terrible.

The new WB uses aliased fonts, which makes them smoother, but reduces readability and crispness. In addition, when font size is set to 10px with zoom, equal as on old WB, I can fit 32 CAPs.

If I turn off resource panel (which means I am turning off needed functionality I need and have on old WB), I can fit in 4 more APs. That makes it to 36 with loss of functionality. That is at 84% zoom.

If I reduce the zoom level to minimum possible (59%), I can still not fit all 44 devices. I can see 40, and half of one more, and the font size is 7 px. Needless to say, fonts are extremely small at that level and it it very hard to manage anything if I have to have magnifying glass to look at stuff. (I wear glasses and don't see very well).

Then, I have that side panel that also takes a lot of space and reduces visibility on the rights side, and the scroll bars are hard to hit because they are too small. - Now imagine working with gloves on a closet dealing with million cables on a client location trying to hit this using Trackpad on T series, hunting successful activation and connection of APs during infrastructure work.

Now, try to do four RBs side by side. Go ahead and try it. There is minim windows size limit, which makes using 4 WBs side by side impossible. All this on a FHD Lenovo T470s tank that I use for terrain work and administration.

This is really not a joke, I can't work like this.

Here is a comparison image on 100% (benign data) (6 mth auto delete img):

Also, the rendering speed is a joke.

Paternot · Fri Dec 13, 2024 8:44 pm

I'm not seeing rendering speed problems, and the fonts are crispy enough for me - and I have bad eyesight. Maybe it's a Windows problem? I'm using Linux, and people using Mac aren´t complaining about this (font aliasing).

ONE thing I saw slowness is when getting firewall rules: it's definitely slower than before.
Some complains of you I share too: bad element contrast and lack of vertical columns are two of them. But I really liked the white/gray thing. It was really clear for me. True, I use it inside. Maybe it's a problem on the field? That I don't know.

This is a beta version, and it's far from cast on stone. Look at the very first post on this thread, and You will see that there are several things not done yet - but that are on the "to do" list.

I think the best You could do is make a post pointing (clearly and without emotions) what the problems are, how they affect You, how You think they can be dealt with and why. Several complains/suggestions on this thread were already implemented - the white/gray lines is one of them.

Go ahead. Do a report, explain Your reasons and give suggestions - but don't rant. This is why this thread is here. Mikrotik IS listening - I've seen it time and again.

atomicduck · Sat Dec 14, 2024 12:35 am

OK, here you go:

General Observations:

The new WinBox is significantly slower compared to the previous version.
Startup time on slower systems is 10–15 seconds compared to the near-instant launch of the old version on weaker systems.
The interface uses more screen real estate, making multi-connection setups inefficient or impossible, especially on smaller screens (e.g., 14").
Horizontal tabbed design is inconvenient. Visual elements have to always be on the same place and look the same.
The lack of vertical separation in tables makes dense data (like CAPs/APs info) harder to read.
Side panel and small scrollbars reduce usability in field conditions, especially with gloves or trackpads.
Minimum window size prevents arranging multiple WinBox instances side by side, which is critical for monitoring multiple devices.

Specific Usability Issues:

Font aliasing reduces text crispness and readability, especially for users with vision impairments.
Gray design patterns look good, but reduce total contrast and make information harder to read.
At default zoom, fewer CAPs fit on the screen compared to the old WinBox:
- Old WinBox: 44 CAPs visible at default settings.
- New WinBox: 32 CAPs visible at 100% zoom.
- At minimum zoom (59%), only 40 CAPs are visible, with a font size of 7px—impractically small for real use.
Resource panel consumes valuable space, limiting the visible device count.
Login screen occupies over 30% of the screen, reducing space for actual work, an issue especially on smaller screens.
Alternating white/gray row colors do not compensate for the lack of contrast or vertical separation in dense data.

Challenges in Real-World Scenarios:

Managing large networks is significantly harder due to reduced information density:
- Networks with 50 APs (300–400 items including virtual APs) suffer from reduced overview due to lower information density.
- Larger networks with 100 APs and 4 SSIDs per frequency (800 APs) become hard to manage.
Fieldwork conditions amplify these issues:
- Using an 11" laptop on-site (e.g., on a crane or in a wiring closet) requires a more compact and functional interface.
- Small scrollbars and inflexible window sizing hinder quick adjustments.
Limited visibility, difficult navigation, and poor contrast make it hard to efficiently manage multiple devices.

Suggestions for Improvement:

Reintroduce or enhance vertical separation in tables for better data visualization.
Allow smaller minimum window sizes for side-by-side device management.
Provide options to disable or minimize non-critical UI elements (e.g., resource panel) to maximize screen space.
Improve font rendering for better readability and crispness, especially for users with vision challenges.
Consider replacing small horizontal and vertical scroll bars with larger version of the same. .
Test the interface in real-world conditions (small screens, gloves, trackpads) to better align with real work needs.

Closing Note:
The new WinBox sacrifices usability for aesthetics, which impacts professionals managing large-scale networks. Addressing issues related to screen density, navigation, and performance would significantly improve the tool’s practicality in real-world scenarios.

**

I personally prefer a real human response to this sanitised version. I deliberately wrote my comments as I did, because I am pretty sure someone in management tasked the team their valuable ideas that lead to this. I work for large companies and see this daily.

To comment on your statements:

Font antialiasing and bad optimisation is the real reason for loss of crispness on non subpixelated screens.
On Macs the WB looks OK, but I don't bother with it due to real estate loss. 27" 5K screen provides literally the same work space as 14" FHD sceen. I use VM Win and old WB.
Rendering speed is terrible. Run a VM Win with 2-4 GB of RAM and one core and try it. It doesn't matter if my workstation can run it fine, but it matters very much if my field i7 machine on battery saving struggles with it.

Cha0s · Sat Dec 14, 2024 2:54 am

Winbox MUST look perfect on the Marketing Department's Macs. Who gives a damn about your measly 14" windows laptop?
Go buy a 17" Laptop. And make it a heavy, power hungry, gaming laptop just to make sure Winbox starts up fast and smooth.
It's your problem, not Winbox 4's lousy design for professionals. :facepalm:

Hell, you should not even use Winbox. How can you call yourself professional and use buttons? You should only use CLI. That's how you prove while hanging from a 15 meter tower, that you are a true professional. No need for colors, and information density and all other "stuff" that we all complain about. Those are for boomers. You should strive to be with the cool kids that prefer no productivity and usability on their software. Or even better, only use touch screens with huge UIs for everything. That's the way to go these days! If you want to be cool, that is...

It's obvious that no market research went into building Winbox 4.
Judging by the result it seems that they only heard some kiddies wining about how "Windows 95" Winbox looks and how it cannot run natively on Macs, and sought to destroy everything that actually made Winbox (and MikroTik RouterOS for that matter - because RouterOS without Winbox is just a glorified locked down linux router) what it is.

I honestly have very little faith that Winbox 4 will ever get as good as Winbox 3, or ever get to feature parity.
We saw it with ROS v7, so we know what to expect by now...

But I would be rather glad for MikroTik to prove me wrong and make Winbox great again. But they won't.

Paternot · Sat Dec 14, 2024 4:03 am

This new version really has some road to travel, before it's production ready. BUT I can say that I used most webfig, since I couldn't stand the old Winbox.

Is the new one perfect?
Hell, no!

Is there some (several?) things I'd like to see addressed?
Oh, Yes! Most definitely.

Is it really slow?
Not sure about it. At some points feels slower, but I'm not sure. Maybe it's something to do with the bandwidth - at some point we had the same problem with the old one.

Does it need a really beefy hardware to run?
Not in my experience. I have one Ryzen 5600X desktop, and it runs fine on Linux. Yes, I know: one 5600X isn't the worst. No, it isn't. But it isn't the fastest either - far from it. Maybe the problem isn't the CPU itself, but the dataset?

jmmikrotik · Sat Dec 14, 2024 9:30 am

please add aarch64 for linux

Cha0s · Sat Dec 14, 2024 3:12 pm

This new version really has some road to travel, before it's production ready. BUT I can say that I used most webfig, since I couldn't stand the old Winbox.

Is the new one perfect?
Hell, no!

Is there some (several?) things I'd like to see addressed?
Oh, Yes! Most definitely.

Is it really slow?
Not sure about it. At some points feels slower, but I'm not sure. Maybe it's something to do with the bandwidth - at some point we had the same problem with the old one.

Does it need a really beefy hardware to run?
Not in my experience. I have one Ryzen 5600X desktop, and it runs fine on Linux. Yes, I know: one 5600X isn't the worst. No, it isn't. But it isn't the fastest either - far from it. Maybe the problem isn't the CPU itself, but the dataset?

Is Winbox 4 more usable than Winbox 3. The answer is no on multiple fronts.
So the net result is: Winbox 4 is a downgrade. It's just as a downgrade today on beta version whatever as it was on beta version 1.

Will it take years (and I am not exaggerating) for MkroTik to bring it anywhere near close the usability levels of Winbox 3?
Yes. Absolutely.

Will MikroTik suddenly deprecate Winbox 3 after a certain RouterOS upgrade, forcing us to use Winbox 4 before it's nowhere near production ready?
You bet your ass they will! That's what they've always done when introducing major changes, and I don't for a second believe that we can continue to use Winbox 3 if we don't like Winbox 4. They WILL stop support for Winbox 3 sooner or later. That's a guarantee.

I don't give a rat's ass about looks. I only care about productivity. I use RouterOS professionally and not as a toy at my home to show off to guests. Looks are not important at all for work tools.
If the tools and UIs of RouterOS hinder productivity, then those tools are bad. As such, Winbox 4 is bad. The whole design/approach is bad. Not some minor details.
Winbox 3 is the epitome of a usability/productivity tool. I don't care if it looks like Windows 3.11. It does the job and it does it WAY better than Winbox 4, and that's all that matters to those of us that use this thing to make a living and cannot waste time on stupid UIs. Some of us use Winbox all day long. Every wasted second on each bad UI decisions and bad/slow implementations accumulates to lost hours per week.
It's obvious that those who designed Winbox 4, do not use it professionally, and their ego is such that cannot listen to anyone's pragmatic requirements for such a tool. ie: productivity/usability over looks.

But hey, it does look good on MacOS (or so they say)! That should count for something, right? How else are we gonna lure in those hipster boys to buy MikroTik routers? ;)

JonathanYoung2161 · Mon Dec 16, 2024 5:05 am

LOVE the new WinBox!!!

I have always wished for a excel feature the ability to resize a column to fit the content by double clicking on the column.

I would love a tab feature so you can go from one device to another faster.

Wish I could open multiple device from the start menu at one time

Overall GREAT JOB!

Mon Dec 16, 2024 9:45 am

@atomicduck

1) what kind of VM are you using, please post some more details, so we can try to replicate the issue
2) a lot of what you mentioned is going to be improved or fixed in the next release, so please give it another chance then

templeos · Mon Dec 16, 2024 1:17 pm

Please fix internal windows position not being saved properly. They keep shifting to the top. It is so annoying.

Positioning window before disconnecting or quitting WinBox:

before closing winbox.png

After reopening WinBox:

position of the window shifted.png

robmaltsystems · Mon Dec 16, 2024 1:56 pm

Forgive me for no reading through six pages but how do we report bugs or suggestions with WinBox beta? Assume there is a github somewhere?

Also, out of interest, what GUI platform is it built on?

Mon Dec 16, 2024 4:02 pm

Please just report here in this topic.

si458 · Mon Dec 16, 2024 4:58 pm

ive just realised i cant edit my vlans on my CRS125-24G-1S using winbox 4!
if i go into switch then vlan, the table is empty?

Screenshot 2024-12-16 at 14.55.47.png

yet open it up in winbox 3 and all vlans and other options are listed there!

Screenshot 2024-12-16 at 14.56.24.png

robmaltsystems · Mon Dec 16, 2024 5:03 pm

Please just report here in this topic.

Not that easy to know whether the fault has been reported already.

atomicduck · Mon Dec 16, 2024 5:58 pm

@atomicduck

1) what kind of VM are you using, please post some more details, so we can try to replicate the issue
2) a lot of what you mentioned is going to be improved or fixed in the next release, so please give it another chance then

Hello Normis.

I had an issue with starting and running WinBox for Mac on Wine, as well as with an older WB beta. I needed to start working ASAP on a new network. The situation was the same on my Win 11 work machine, so I used an older Win 10 LTSC VM and successfully got the job done. I reported this under SUP-173297, but since it was urgent, I didn’t spend time debugging and just did everything in the VM.

Later (after I finished the work), I installed updates on Sonoma, used Onyx, and installed the latest WB 4 beta. It then started working, but I don’t know what the actual issue was. On my Win 11 machine, I didn’t bother investigating and continued using Win 10 LTSC. Currently, I’m testing and optimizing FT.

For speed testing of the WB beta, you can use any slowish Windows virtual machine. I’m using VMware 17.6.0 on Windows and Fusion 13.6.1 on Mac, and they perform about the same.

If you install a Windows 10 or 11 VM with limited resources (e.g., 2 cores, 4 GB RAM), you’ll easily notice rendering slowness when resizing or moving windows. The more you limit the VM, the more rendering issues (slowness, glitches) you’ll notice. The rendering engine simply isn’t optimal currently. All this testing is being done on a Lenovo T470s with 16 GB RAM that I work with (because it is built like a tank, still sleek with two batteries, and has a full size RJ45 port).

As for the other issues, I really hope it is so. I wrote my comments in good faith, but mind both I and some of my colleagues share the same sentiments, tho they are more silent then I am.

To end in a good spirit: I am impressed how well you optimised the AC and AC XL with Wave 2 drivers and new Capsman on 17.6. On my testing I got roughtly 650mbps DL on with single client, compared with 750 on my XV2-2X that runs AX chipset. - Same room, same distance. Not sure yet how they will behave in industrial/warehouse setting, but I am highly optimistic. The main reason I prefer MT / WB approach to other is that I am able to monitor and optimise entire site easily. That is why I am so concerned with the loss of information density and usability in new WB.

dang21000 · Mon Dec 16, 2024 7:26 pm

Like logs, see vlans ports members are hard ; long line content must be more readable.

Tue Dec 17, 2024 10:08 am

I was asking because we can't repeat any slow performance on older Windows machines. Are you testing the latest WinBox beta? There were performance fixes in one of the later versions.

Also, in your virtual machine software, have you enabled 3D acceleration checkbox in VM settings?

nishadul · Tue Dec 17, 2024 2:09 pm

Hello,

Could you please help me, How to change date format as like DD-MM-YYYY or DD-MMM-YYYY

guywifi · Tue Dec 17, 2024 4:33 pm

Where does linux version stores 'saved routers'? Is there a way to import Winbox Loader Addresses?

Did you get an answer to this?

Hejsan · Tue Dec 17, 2024 7:20 pm

I can't find it or maybe this feature hasn't been implemented yet.
In version 3 there was an option to save all connections under a master password. Is this in the new version?

I have exported all connections from WinBox v3.41 (I had a master password there) and imported this file in v4.0... it worked perfectly. I am asked for this master password every time I open WinBox 4.0

teslasystems · Tue Dec 17, 2024 10:24 pm

Just noticed that I can drag files from folder to WinBox, but can't drag them from WinBox to folder. Also, if a file has zero size, it shows an error. OS Windows.

belthesar · Fri Dec 20, 2024 7:11 pm

@atomicduck

1) what kind of VM are you using, please post some more details, so we can try to replicate the issue
2) a lot of what you mentioned is going to be improved or fixed in the next release, so please give it another chance then
Hello Normis.

I had an issue with starting and running WinBox for Mac on Wine, as well as with an older WB beta. I needed to start working ASAP on a new network. The situation was the same on my Win 11 work machine, so I used an older Win 10 LTSC VM and successfully got the job done. I reported this under SUP-173297, but since it was urgent, I didn’t spend time debugging and just did everything in the VM.

Later (after I finished the work), I installed updates on Sonoma, used Onyx, and installed the latest WB 4 beta. It then started working, but I don’t know what the actual issue was. On my Win 11 machine, I didn’t bother investigating and continued using Win 10 LTSC. Currently, I’m testing and optimizing FT.

For speed testing of the WB beta, you can use any slowish Windows virtual machine. I’m using VMware 17.6.0 on Windows and Fusion 13.6.1 on Mac, and they perform about the same.

If you install a Windows 10 or 11 VM with limited resources (e.g., 2 cores, 4 GB RAM), you’ll easily notice rendering slowness when resizing or moving windows. The more you limit the VM, the more rendering issues (slowness, glitches) you’ll notice. The rendering engine simply isn’t optimal currently. All this testing is being done on a Lenovo T470s with 16 GB RAM that I work with (because it is built like a tank, still sleek with two batteries, and has a full size RJ45 port).

As for the other issues, I really hope it is so. I wrote my comments in good faith, but mind both I and some of my colleagues share the same sentiments, tho they are more silent then I am.

To end in a good spirit: I am impressed how well you optimised the AC and AC XL with Wave 2 drivers and new Capsman on 17.6. On my testing I got roughtly 650mbps DL on with single client, compared with 750 on my XV2-2X that runs AX chipset. - Same room, same distance. Not sure yet how they will behave in industrial/warehouse setting, but I am highly optimistic. The main reason I prefer MT / WB approach to other is that I am able to monitor and optimise entire site easily. That is why I am so concerned with the loss of information density and usability in new WB.

It sounds like your Lenovo is set up as a Hackintosh. Are you aware that there's a native macOS build for Winbox 4? It might be worthwhile for you to eschew trying the VM route when you can run the native version, without any of the headaches of virtualization. That said, if the VMs are largely there for work vs. personal isolation, I'd make sure that you've configured your VM with any GPU acceleration you can. Qt, like other modern GUI frameworks, takes advantage of a GPU to accelerate its rendering, and falling back to software rendering is going to hurt no matter what OS you're using.

WRT the new need for GPU acceleration, it seems like the target era for acceleration is DirectX 11 support (based on other screenshots in the forum). That came out in 2009, which means that any machine, even with an onboard GPU, has had support for the feature set needed for over a decade. It is indeed a new requirement above and beyond the legacy Winbox codebase, but it's really not a tall ask. Folks have every right to be grumpy about the new requirements, but it's unfair to be mad that there's a much more supportable code base than its predecessors and also be mad that the new codebase comes with new requirements. There's plenty that still needs love in Winbox 4, but in my opinion, the new app is a huge step in the right direction in multiple dimensions, and while my needs aren't the same as everyone's, it's been more than sufficient for me to maintain my networks.

I kinda robbed this reply to send my thanks to normis and anyone else working on the new Winbox, because I know there's an awful lot of negative feedback here. Not my place to comment on their feedback, but I know hearing a lot of negative responses can really take the wind out of your sails, so I hope that hearing that there are folks that are thankful for your work helps you continue.

ksteink · Sat Dec 21, 2024 3:05 am

I just installed the Beta 14 and looks good. Few things that I like to see in future versions:

- A way export current DB of devices registered. I found import but I couldn't import the .WBX from version 3.41 so I had to input manually my devices. For large deployments it's not practical

- A quick search to find by Workspace, Group, Comment or IP Address / Hostname. For multiple devices can be cumbersome to find the device.

- The Font of all the text is too small!!! Common my eyes are not as use to be (At least give the chance to adjust it at the taste of the user!)

I will find more stuff for sure but this is my first impressions by trying out the new version!

SuperMarioSF · Sat Dec 21, 2024 2:35 pm

There is a way to crash WinBox 4.0beta14.

In a x86 based system (normal x86, or a x86 CHR), open System/Console, double click the item that should be the local screen console, and it will just crash.

crash.png

For reference, in Winbox 3, double click that item do nothing at all.

SuperMarioSF · Sat Dec 21, 2024 2:45 pm

Another bug for beta14.
For some reason the timezone droplist in System/Clock duplicated each item one more time, except for "manual" option which only present once.

This bug seems only present when connected to a RouterOS 7.x device.
When connected to a RouterOS 6.x device there is no duplication problem.

duplicated_item.png

brevilo · Mon Dec 23, 2024 10:26 am

Awesome news!

Now, I tested 4.0beta1 and 4.0beta3 on macOS (Sonoma on M3, against ROS 7.15.3) and it fails to connect with the following (WinBox 3 via Wine still OK):
Code: Select all
ERR: Could not connect, MacConnection syn timeout
(while at it, please allow for copying error messages)

If only you'd taken the opportunity to change that meaningless (if not entirely misleading) name, now that its Windoze shackles are finally off :)

Thanks and keep it up!

Unfortunately, no change with 4.0beta14 (now against ROS 7.16.2)...

JunoBox · Tue Dec 24, 2024 12:14 pm

Version 4 is looking nice and awesome, a small missing in the Log windows is that I can't still find the Freeze button to quick stop logs stream, that's a requirement!
Also when opening the log window. I always have to scroll completely first to the newest additions. With WinBox 3 it always jumped directly to the newest entry when opening the log window, regardless how the sorting is defined (newest or oldest on top).

Another point of improvement. Workspaces. Make it switchable to auto-save on/off. Sometimes I made changes temporarily in for example columns and do not want this to be saved to the workspace. I would like to click a save button by my self when I think it is needed.

Thu Dec 26, 2024 11:34 am

1. Please implement "select all" aka Ctrl+A to mark all entries
2. Please implement selecting with keyboard => Shift+arrows
3. If you carefully selected some entries and by chance you click anywhere outside checkbox area than all selected items get unselected - what an annoying situation.

NTheZone · Mon Dec 30, 2024 7:31 pm

Please bring back in-line comments, no matter the reason. Do not remove functionality; adding is OK or updating is fine, but removing is just BAD.

Running under MacOS, x86

UPDATE: I see that the option is not under the column selections, but under the hamburger menu on the top right. It would however, still be nice to rearrange the column order.

NTheZone · Mon Dec 30, 2024 7:36 pm

Also the drop down of side options was nice. Now I have to add another click to get under other options, e.g. IP --> Firewall & IP --> DHCP Server

Wherever there is an added click, is another means of lost productivity and hassle.

inazmul · Wed Jan 01, 2025 8:52 pm

I just installed the Beta 14 and looks good. But I cant using New Winbox Option, After I click On It then existing winbox will crass, Where I let them the issue

By the way I can't replay the post the announcements of WinBox 4 Is here any Problem on that ??

spippan · Thu Jan 02, 2025 5:26 pm

...

@inazmul

why are you using my avatar picture?

inazmul · Thu Jan 02, 2025 11:29 pm

Some Time WinBox 4 Take too may times, I feel leggy. I think it's need more speed

Another problem is drag and drop, I taka my router backup, after that try to drag it my pc can't. it's an issue for me

inazmul · Thu Jan 02, 2025 11:30 pm

...
@inazmul

why are you using my avatar picture?

I like you avatar, by the way I just change it. :P

xsherlock · Fri Jan 03, 2025 3:10 pm

Is there some limit on the router OS version that is compatible with the new winbox?
I have RB751G-@HnD running 6.42.12 and and new Winbox will not connect to it ?
By mac or IP it is stuck in Authentication.

Maciej

Fri Jan 03, 2025 3:23 pm

The same is true for newer WinBox3. We improved security, so you need to upgrade RouterOS in any case.

xsherlock · Fri Jan 03, 2025 3:25 pm

can it still be ver 6 or new winbox4 is only compatible with version 7?

Fri Jan 03, 2025 3:34 pm

You can use v6. Sorry I misread your post, Winbox will not work with versions older than v6.42.12, but your v6.42.12 will be fine.

Vaelen · Sun Jan 05, 2025 2:58 am

I know there are still things to work out but wanted to say how much I appreciate the linux build! And bringing us a flatpak to boot.
Finally no more Wine install.

nmt1900 · Wed Jan 08, 2025 4:21 pm

@normis and others working on Winbox 4 should prioritize SUP-175441

rextended · Wed Jan 08, 2025 6:03 pm

@normis and others working on Winbox 4 should prioritize SUP-175441

And for what reason?

Jotne · Wed Jan 08, 2025 8:29 pm

What is SUP-175441? No information on the forum about that support request.

hashbang · Thu Jan 09, 2025 7:37 pm

Good to see linux version. It was long awaited.
copy button in dialogue box missing
filter ppp interfaces by vlan or if.
thnx

nmt1900 · Thu Jan 09, 2025 7:45 pm

Another bug
CRS112-8G-4S with 7.16.2 - Switch-> VLAN window fails to populate - not just configuration (VLANs and ports) but even tabs are missing while Winbox 3 shows configuration correctly. Selecting other workspace or logging in another way (via RoMON instead of straight IP address) does not remediate this issue.

snap 2025-01-09 at 19.31.57.png

I have one CRS226 series switch with 7.15.3 and this problem does not appear on that one.

OOJSPI · Thu Jan 09, 2025 11:14 pm

How can I run this software in Sandboxie? I tried a variety of settings, but WinBox just refuses to be sandboxed... Does it use some kind of low level kernel access? Does it actually encrypt traffic between client and router? There is no way to apply a TLS certificate to WinBox in "IP Services".

CGGXANNX · Fri Jan 10, 2025 3:22 am

I found this about WinBox encryption https://margin.re/2022/02/mikrotik-auth ... -revealed/. No idea if the author was correct or whether it's still relevant to the current version.

Amm0 · Fri Jan 10, 2025 4:38 am

I found this about WinBox encryption https://margin.re/2022/02/mikrotik-auth ... -revealed/. No idea if the author was correct or whether it's still relevant to the current version.

It's actually documented as ECSRP for key exchange and authentication [...] AES128-CBC-SHA as an encryption algorithm:
https://help.mikrotik.com/docs/spaces/R ... ox-Summary
(and I believe winbox4 uses exact same protocol as winbox3)

In the TLS wish, I'd like to see X.509 client authentication for winbox protocol (and REST API).

CGGXANNX · Fri Jan 10, 2025 7:01 am

Which match the information from that article. So, I guess the details provided might still be correct.

Fri Jan 10, 2025 12:43 pm

Some very long awaited changes in the new release, check it out! Remember to check side menu for some new options:

What's new in 4.0beta16:

*) Redesigned table view
*) Implement column reordering
*) Implement table find feature
*) Implement table row colors defined in WinBox files, such as for log, route, etc.
*) Allow table's right-side menu to be collapsed under a dropdown
*) Make disabled table rows more readable
*) Improve scrolling experience
*) Move table's selected rows count label before the filtered count label
*) Change the style of the focused table row and only show it when it has keyboard focus
*) Add app setting to change table row padding (height)
*) Add app setting to toggle table column separators
*) Add a "Select All" checkbox in the table header
*) Add some executable properties details for Windows
*) Add Ctrl+A, Home, End, Page Up, and Page Down shortcuts for table navigation
*) Fix occasional crashes in Windows when updating or using "New WinBox"
*) Fix table navigation with Shift and Cmd keys on macOS
*) Fix neighbor discovery when multiple instances are opened in Windows
*) Fix IPv6 neighbor discovery on Windows OS, which should now work with multiple active interfaces

mozerd · Fri Jan 10, 2025 1:17 pm

Very nice improvemnets ... starting to like Winbox v4 ... NICE ...

Fri Jan 10, 2025 1:31 pm

OMG ... I see columns ... thank you ... however the problem of deselecting selected rows if you click any row outside select column still exists

CGGXANNX · Fri Jan 10, 2025 1:38 pm

Many thanks! This update improves the information density a lot. And the tables are now much more readable with the grid columns👍.

My only remaining wish feature is the option to select the system font (Segoe UI) as alternative (the current font is unfortunately blurry at 84% and 94% zoom, and it has variable widths for the digits) and I can see myself switch to using WinBox 4 fulltime.

nkourtzis · Fri Jan 10, 2025 1:45 pm

Please:

1. Implement multiple column sorting for all tables (even the connections table shown at launch)
2. At the connections table, please add a column with the RoMON Agent (or even better, an option to show/hide columns)
3. Increase the contrast a bit in dark mode, so that for example, inactive flags of various items are more visible

woland · Fri Jan 10, 2025 2:10 pm

The feature I´m missing most are quick filter fields for every table, in every column...

Fri Jan 10, 2025 2:12 pm

You can already filter by column, or you mean, you want it to "look" like excel?

rextended · Fri Jan 10, 2025 2:58 pm

I love Excel ( 😛 )

woland · Fri Jan 10, 2025 3:00 pm

You can already filter by column, or you mean, you want it to "look" like excel?

Thanks @Normis, yes, but in Excel you have many options with a roll down menu. A simple field in each column, where you could just enter a string and wildcards (or maybe a regex if the devs feel fancy) to match the rows.
Similar function like grep. That´d be really useful!

woland · Fri Jan 10, 2025 3:03 pm

I love Excel ( 😛 )

A bit off topic here, but I hate Excel.🤮 Still I have to use it and I find the filter function very useful.

gigabyte091 · Fri Jan 10, 2025 3:34 pm

a8be9894-001d-4a10-8d68-eff9f3bad352_text.gif

What's with the Mikrotik Excel ??? Why ? It so ugly... Not modern at all...

Also when will you bring back LTE graphs ?

woland · Fri Jan 10, 2025 3:41 pm

What's with the Mikrotik Excel ??? Why ? It so ugly... Not modern at all...

Oh my, oh my! CLI & Fat Clients are also not modern, let´s get rid of them. MT should focus on WebGUI hosted on the cloud only!

Atmis · Fri Jan 10, 2025 3:50 pm

The table mode is much more readable, thank you !

It would be nice to be able to automatically resize a column to the widest value by double clicking the right space between two columns in the title bar (just like Excel 😜)

gigabyte091 · Fri Jan 10, 2025 3:51 pm

Wait wait, so they want to make more modern WinBox and then they do this ? At least give us an option to turn that off if possible...

Fri Jan 10, 2025 3:55 pm

Turn what off?

gigabyte091 · Fri Jan 10, 2025 4:06 pm

This new table view.

elbob2002 · Fri Jan 10, 2025 4:27 pm

Table view is fantastic. It was the one feature I missed the most. Makes everything much more legible.

I think the only feature left that I don't like is when using inline comments - the comment is the second column instead of at the end!

Fri Jan 10, 2025 4:31 pm

So why not allow some winbox.cfg where all that bells and whistles could be set on/off?

gigabyte091 · Fri Jan 10, 2025 4:35 pm

So why to not allow some winbox.cfg where all that bells and whistles could be set on/off?

Agreed.

Ullinator · Fri Jan 10, 2025 4:59 pm

*) Implement table row colors defined in WinBox files, such as for log, route, etc.

Thank you very much, that´s the feature I missed most :-)

mszru · Fri Jan 10, 2025 5:45 pm

The feature I´m missing most are quick filter fields for every table, in every column...

That's what I would also like to see implemented. In the application I use it is called "Instant Filter" or "Filter Row" that you can show or hide when not needed.
When it's on you can see a filter box underneath each column header along with the operation applied:

Filter Row On.png

The set of applicable operations is shown in a dropdown list when you click the icon of the currently selected operation and depends on a column type. In the example above icon [A] means "Contains" operation is selected and it will look for a sub-string in the column's values. For text fields the following operations are possible: Starts with, Ends with, Does not contain, Is empty, Is not empty, etc. Numeric fields can be filtered using operations like Equals, Greater than, etc. Enumeration fields may be filtered using Equals and Does not equal operations.

When it's off, it looks like a normal table header:

Filter Row Off.png

It is far more convenient way of filtering table data comparing to the current implementation.

The need for the “Find” field is, from my point of view, a consequence of the inconvenience of using the current filter implementation, cause when you are looking for something in a table you are likely expecting to find the value in a certain column anyway (e.g. error message in the "Message" field in case of Log). I don't use "Find" and I think it can be removed if the "Filter Row" is implemented.

carlosjs23 · Fri Jan 10, 2025 6:32 pm

How can I export back the connection list from Winbox 4 to Winbox 3.

sirbryan · Fri Jan 10, 2025 8:10 pm

Just loaded the new beta and this is feeling more comfortable. The quick access buttons on the right instead of tabs for the grouped sections is a good compromise, and the table is much more legible.

Are the table columns separators and group-quick-access-buttons-now-placed-above-action-buttons (formerly known as tabs) coming to Webfig?

And +1 for zebra coloring of rows (at least as an option). Soooo helpful on long lists of routes, IP DHCP leases, BGP sessions on route reflectors, and firewall rules.

teslasystems · Fri Jan 10, 2025 10:19 pm

Thank you very much for adding a grid and ability to change row height.

Regarding scrolling, I don't know, what you've done with it, but autoscroll in the log window has stopped working.
UPD: it works partially. If you just open the log window and don't do anything, it's ok. But if you scroll up and then scroll back to the latest record, it doesn't autoscroll anymore until you reopen the window.

And after adding gridlines, the problem with random line width on a 150% scaled displays is now much noticable and worse. Some lines are 1 px width, some 2 px.
.

LineWidths.png

Paternot · Fri Jan 10, 2025 10:26 pm

You can already filter by column, or you mean, you want it to "look" like excel?

I don´t know about Excel - but he said "multiple".
I think (THINK) that he want to be able to sort by (say) IP, and THEN by (for example) signal strength. A "multiple sort", if I understood it right.

woland · Sat Jan 11, 2025 11:55 am

I think (THINK) that he want to be able to sort by (say) IP, and THEN by (for example) signal strength. A "multiple sort", if I understood it right.

If you mean myself, no my post was not about sorting, but about filtering. Exactly like in the picture as in the post of @mszru .

infabo · Sat Jan 11, 2025 12:22 pm

I don't like these "thick borders" every few lines. Is this a rendering bug or on purpose (it looks ugly and distracting)?

winbox-table.png

infabo · Sat Jan 11, 2025 12:35 pm

This new table view.

While I wasn’t a fan of the large padding in the "zebra table" view, I did appreciate the zebra-style itself, as it’s a well-recognized UI pattern. Removing this view entirely, without allowing users to toggle between the "classic table" and "zebra table," feels like a step backward. Don’t get me wrong - striving for improvement is always good, and the better often replaces the good. But you first have to find out - which is good and which is better.

A better approach might be to include telemetry in the builds to collect data on user behavior. For instance, track which settings or options from the side menu are most frequently changed or activated. After a defined period, analyze the data. If, for example, 95% of users prefer the classic table over the zebra table, then it makes sense to retire the feature. The same logic could be applied to other settings.

nmt1900 · Sat Jan 11, 2025 5:44 pm

I think that zebra table works better with larger padding - and larger parring has been a regression in usability. Now we have a possibility to adjust the padding even down to 0 value. Classic table view seems to work better with decreased padding. Other welcome addition is the possibility to toggle column separators on and off.

Sun Jan 12, 2025 12:36 pm

I don't like these "thick borders" every few lines. Is this a rendering bug or on purpose (it looks ugly and distracting)?

Someone counts using octal base

Edit:

...And after adding gridlines, the problem with random line width on a 150% scaled displays is now much noticable and worse. Some lines are 1 px width, some 2 px.

Think, that some columns start and end with gridded separator so these separators "add" to doubled line ... same with already mentioned horizontal ones for 8 items grouped for some reason.

Sun Jan 12, 2025 1:18 pm

After some time of "torching" the pooling error appears.

teslasystems · Sun Jan 12, 2025 7:42 pm

I don't like these "thick borders" every few lines. Is this a rendering bug or on purpose (it looks ugly and distracting)?
Someone counts using octal base :)

Edit:
...And after adding gridlines, the problem with random line width on a 150% scaled displays is now much noticable and worse. Some lines are 1 px width, some 2 px.
Think, that some columns start and end with gridded separator so these separators "add" to doubled line ... same with already mentioned horizontal ones for 8 items grouped for some reason.

No, this problem appears only on scaled displays. And not only with grid, it's everywhere: frames, separators, etc. If you have standard screen with no scaling is OS, everything is fine. My assumption is that the line width is calculated "on the fly" while rendering, but there is a very strange rounding. With 150% scaling the line width is calculated like 1*150%=1.5 pixels. But sometimes it's rounded to 1, sometimes to 2 for unknown reason. If I was writing this app, I would calculate the line width on app initialization and recalculate it when OS sends DPI change message. Then use this value while drawing the interface and everything will be fine. And, as a bonus, no unneeded calculations while drawing.

I think, infabo has the same problem. infabo, do you also have HiDPI screen with 150% scaling in OS? Or maybe some other scale value? On my screen, all horizontal lines have the same thickness and it's either 1px or 2px, depending on height of the log window.

Sun Jan 12, 2025 8:21 pm

...
If I was writing this app, I would calculate the line width on app initialization and recalculate it when OS sends DPI change message. Then use this value while drawing the interface and everything will be fine. And, as a bonus, no unneeded calculations while drawing.
...

Suspect that it could be a library problem.

Mon Jan 13, 2025 9:12 am

UPD: it works partially. If you just open the log window and don't do anything, it's ok. But if you scroll up and then scroll back to the latest record, it doesn't autoscroll anymore until you reopen the window.

This is by design. It works like this in any other software. Once you scroll manually, autoscroll stops.

Mon Jan 13, 2025 9:13 am

You can already filter by column, or you mean, you want it to "look" like excel?
I don´t know about Excel - but he said "multiple".
I think (THINK) that he want to be able to sort by (say) IP, and THEN by (for example) signal strength. A "multiple sort", if I understood it right.

But the question was about Filter, not about Sort. And there is already a Filter button, that lets you filter by any column, and by multiple columns.

woland · Mon Jan 13, 2025 10:43 am

But the question was about Filter, not about Sort. And there is already a Filter button, that lets you filter by any column, and by multiple columns.

My idea is only about usability for filtering: pls. see the image from the post from @mszru.
I appreciate that the filter function is implemented. I find a quick filter field per column is more usable. Searching for a specific field in the current implementation is not easy, just look at this exceedingly long roll down menu if you open the filter menu in the firewall box:

Having a quick filter field row scales just better.

Vaxter · Mon Jan 13, 2025 10:52 am

Just to report that version string in info.plist on Mac is wrong, and it never changes with new update.
Version always shows 0.1 which causes apps to scan for updates, like MacUpdater or Latest, to always show that there is a new version od WinBox.

teslasystems · Mon Jan 13, 2025 11:20 am

UPD: it works partially. If you just open the log window and don't do anything, it's ok. But if you scroll up and then scroll back to the latest record, it doesn't autoscroll anymore until you reopen the window.
This is by design. It works like this in any other software. Once you scroll manually, autoscroll stops.

Then it's a very bad design. It beta14 it worked fine, but you desided to broke it? And now, if I'm looking for older records and return back to monitor something in real time, I need to reopen the window to make it work. This is cr*p. WinBox 3 also works, though there is a bug and it reacts only on every second added record.

Clarification: it's ok, that autoscroll stops when you scroll to older records. But when you return back to the very end of the list, it should become working again.

infabo · Mon Jan 13, 2025 3:40 pm

@teslasystems I have none of such issues with any other software on my device. So it is either a Qt-bug or the result of bad border calculation/settings only visible when doing "non-fractional scaling".
I am at 108dpi and may be the cause. As this is not a integer-multiple of 92dpi. But 108 is my native monitor DPI value reported by EDID (and not some "dumb user error")

OKNET · Mon Jan 13, 2025 4:14 pm

Is it possible to have buttons NEW+REMOVE separated from ENABLE+DISABLE like in old winbox ?
It could be easy to slide mouse over "remove" while trying to disable.
Also is it possible to have description popup while hover over single row property, i.e. ip->route DAC = D-dynamic, A-active, C-connect ??

teslasystems · Mon Jan 13, 2025 4:15 pm

@teslasystems I have none of such issues with any other software on my device. So it is either a Qt-bug or the result of bad border calculation/settings only visible when doing "non-fractional scaling".
I am at 108dpi and may be the cause. As this is not a integer-multiple of 92dpi. But 108 is my native monitor DPI value reported by EDID (and not some "dumb user error")

Well, then the line width is incorrectly calculated when a scaling is >100%. Not only when it equals to 150%. I'm sure it's not a Qt-bug, because other Qt apps don't have such line drawing issues.

Mon Jan 13, 2025 4:16 pm

....it's ok, that autoscroll stops when you scroll to older records. But when you return back to the very end of the list, it should become working again.

Yes and no

If you want to check/verify sth in the log and the autoscroll is stopped then if you are back to the end of a list it shouldn't start scrolling by itself as you may want to compare "the latest before stopping" values to the older ones and if you want to jump back & forth there could be no data to compare to as autostarted autoscroll would move the "data window" past the interesting data.

teslasystems · Mon Jan 13, 2025 4:25 pm

....it's ok, that autoscroll stops when you scroll to older records. But when you return back to the very end of the list, it should become working again.
Yes and no :)
If you want to check/verify sth in the log and the autoscroll is stopped then if you are back to the end of a list it shouldn't start scrolling by itself as you may want to compare "the latest before stopping" values to the older ones and if you want to jump back & forth there could be no data to compare to as autostarted autoscroll would move the "data window" past the interesting data.

Don't clearly understand what do you mean, but there is a 'Freeze' button for such purposes in v3 if you want to completely stop autoscrolling. And now there is no this button and everything became only worse. A scrolling experience is not improved as the changelog states, it has degraded.

Just make it as it was in beta14 and add a 'Freeze' button if someone needs to stop autoscrolling at the very end of the list.

w0lt · Mon Jan 13, 2025 4:29 pm

I the "Windows" version of WinBox, I could use an existing "session" as a template so I wouldn't have to start from scratch every time on a new device but yet save it (save as) a different session IP address so I wouldn't mess with what I had already created. How do I do that using the new MAC version of WinBox..or can I yet?

w0lt · Mon Jan 13, 2025 4:36 pm

In the latest version of winBox for MAC, how do I "Check For Updates" in the packages section ? I don't seem to see a button to do that or easily change what version I want to use I/e/ Stable, Testing..etc ? I know you can do it from the Command Line so is this something I have to wait for or is there a work around?

teslasystems · Mon Jan 13, 2025 5:41 pm

More about scaling problems.

Just noticed, that it touches EVERYTHING. Not only the lines. Fonts and icons are also "jumping" and have random size.
Here is an example where it's clearly visible. Original icon size in my case is 26x26 px, after changing a window height it has become 26x25 px. And button captions look like "clipped" and "faded" on the bottom. Other text has also changed (columns captions etc.), but it's not so noticable visually.
.

Buttons.png

Edified · Mon Jan 13, 2025 10:37 pm

New Tables with Settings > Padding: 0 is wonderful. Thank you.

Screenshot 2025-01-13 at 12.37.12 PM.png

Mon Jan 13, 2025 10:47 pm

More about scaling problems.

Just noticed, that it touches EVERYTHING. Not only the lines. Fonts and icons are also "jumping" and have random size.
Here is an example where it's clearly visible. Original icon size in my case is 26x26 px, after changing a window height it has become 26x25 px. And button captions look like "clipped" and "faded" on the bottom. Other text has also changed (columns captions etc.), but it's not so noticable visually.

Could you check it using another computer,another OS, another video drivers etc.?
But on the other hand zoomin WinBox gives: