Winbox v3.22 released!

emils · Wed Mar 11, 2020 12:21 pm

What's new in v3.22:

*) added 24x24 and 32x32 icon support (RouterOS v6.47 required);
*) added Legacy Mode (disabled by default) to allow using older, less secure connections to RouterOS older than v6.43;
*) added scroll bar support in item property windows;
*) added support for super low DPI - 72, accessible by Zoom Out;
*) fixed Log window drawing on HiDPI displays;
*) fixed Zoom In/Zoom Out setting persistence after window is closed;
*) made table row height 15px by default;
*) use monospace font for big pop-up messages;

If you experience version related issues, then please report them to support@mikrotik.com.

Both Winbox 32-bit and 64-bit versions are available here:
https://www.mikrotik.com/download

roe1974 · Wed Mar 11, 2020 12:50 pm

winbox64 is always opnening in a small window.....see picture

Unbenannt.JPG

emils · Wed Mar 11, 2020 12:55 pm

The window size should be stored in session file. Make sure you have autosave on or save the session before closing.

roe1974 · Wed Mar 11, 2020 12:59 pm

auto-save is enabled ..... also tried save it manually .... no change

PS: Also winbox itself starts every time on the left corner of the desktop ......
System: Windows 10(1909) 64Bit

Wed Mar 11, 2020 1:16 pm

Is the only problem the size? Are, for example, opened windows re-opened? Are you sure that you have launched WinBox loader with administrator privilegies, session is selected on WinBox loader before you access router (is not set to "<none>")?

Chupaka · Wed Mar 11, 2020 1:19 pm

I'm in love with new Log window

CZFan · Wed Mar 11, 2020 1:23 pm

winbox64 is always opnening in a small window.....see picture

I am not experiencing the same, Windows 10 version 1803

CZFan · Wed Mar 11, 2020 1:24 pm

I'm in love with new Log window

Ditto

roe1974 · Wed Mar 11, 2020 1:28 pm

Is the only problem the size? Are, for example, opened windows re-opened? Are you sure that you have launched WinBox loader with administrator privilegies, session is selected on WinBox loader before you access router (is not set to "<none>")?

yes, only problem is the size
when i have rezized the session and put it on the taskbar an re-open the session ... size is OK ... closing the session and reopen with winbox loader ... size is small
no change if starting with or without admin privileges
i start winbox loader an double click the saved connection ....

richard

Sob · Wed Mar 11, 2020 2:09 pm

There's a bug with read-only fields and copying to clipboard. I discovered it when I tried to copy log messages (after double clicking line in log window), but it's actually not new, same happens also in older WinBox with other fields:

winbox-readonly-copy.png

- If I double-click the field to select whole text (A) and try to copy it to clipboard using keyboard shortcut (Ctrl+Ins / Ctrl+C), it works correctly.
- When I select only part of text (B) and try to copy it, keyboard shortcuts don't do anything. Copying from context menu (right click on selected text, Copy command) works.

Then there's tiny little detail about font in system note popup, it's much wider than in Terminal. IMHO it would look better it used the same one, i.e. what is now in Terminal should be also in popup (definitely not the other way around). Just for the record, it's no biggie.

Other than this, everything is perfect.

anav · Wed Mar 11, 2020 2:16 pm

Only MT nerds would be in love with 0s and 1s displayed on the log palette ......... ;-P

As for me, same same, garbage looking as per the previous version

(

gemesif · Wed Mar 11, 2020 2:23 pm

I'm in love with new Log window

Thanks for MikroTik, the professional works.

roe1974 · Wed Mar 11, 2020 2:34 pm

i deleted all files in C:\Users\xxxx\AppData\Roaming\Mikrotik\Winbox\sessions and C:\Users\xxxx\AppData\Roaming\Mikrotik\Winbox and started winbox from stretch.
issue persists .....
OS: Windows 10 Version 1909 (Build 18363.719)

Richard

Wed Mar 11, 2020 2:45 pm

did winbox re-create those deleted files? meaning, did winbox actually save something new in session file?

complex1 · Wed Mar 11, 2020 2:52 pm

winbox64 is always opnening in a small window.

No issues here, running fine on Win10 1909 b18363.719

roe1974 · Wed Mar 11, 2020 2:53 pm

did winbox re-create those deleted files? meaning, did winbox actually save something new in session file?

yes ... new files are here
back to 3.20 .. everything is normal .... window positioning works.....
then back again to 3.22 .... opening first time the winobox ... position OK ... opening first session ..... position OK
closing session&winbox .... opening winbox /session again ... position not OK ... and stays not OK .... strange

Richard

PS: Resolution 3840 x 2160

Wed Mar 11, 2020 2:57 pm

Can you please send this session file to support@mikrotik.com?

roe1974 · Wed Mar 11, 2020 3:11 pm

Can you please send this session file to support@mikrotik.com?

mail sent

br, Richard

td32 · Wed Mar 11, 2020 3:23 pm

I confirm session windows inside main winbox windows are saved but their size seams to be restored to a kind of default preset size at each start

first start windows set up

on new session, also the same on winbox restart

roe1974 · Wed Mar 11, 2020 3:28 pm

session window full-screen works and is saved......
but all between "wrong-small-size" window and full-screen is not saved.....
Richard

roe1974 · Wed Mar 11, 2020 3:29 pm

Can you please send this session file to support@mikrotik.com?

FYI:
MikroTik support #[SUP-10870]
Richard

nishadul · Wed Mar 11, 2020 3:43 pm

Thank you for new Log Window.
** In Log Window, # column align need Left OR Center because # and Time is show very near/close.
** Zoom In and Zoom Out need shortcut key as like: Ctrl +, Ctrl -

w0lt · Wed Mar 11, 2020 4:53 pm

Also, when upgrading the firmware, within the "Routerboard dialog box", the message to reboot your computer to activate firmware is off centered.

Paternot · Wed Mar 11, 2020 5:16 pm

winbox64 is always opnening in a small window.....see picture

Unbenannt.JPG

Linux + Wine here.
Windows opens with the last used size and position.

roe1974 · Wed Mar 11, 2020 9:18 pm

tested another machine (Also Lenovo Laptop) with same Win10 Version .... same issue

I have on both laptops german localization .....

Richard

mszru · Wed Mar 11, 2020 10:37 pm

The issue with Winbox window position and shuffled windows inside the Winbox itself is caused by the scaling factor in the display settings.
If you set it to 100%, you won't see any issues. In my case it is set to 125%...

Windows 10 build 1909 Display Settings.png

MichalPospichal · Wed Mar 11, 2020 10:51 pm

I also confirm that saved opened windows inside Winbox are always reverted to some default sizes after each login. I have scaling set at 100%, 2K display.

roe1974 · Wed Mar 11, 2020 11:10 pm

tested another machine (Also Lenovo Laptop) with same Win10 Version .... same issue
I have on both laptops german localization .....

Richard

OK ... Windows 10 Display scale factor set to 100% and there is no problem.
when i set the scale to 125% or 150% (as i use the notebook) the issue is back

Richard

macsrwe · Thu Mar 12, 2020 2:10 am

The window size should be stored in session file. Make sure you have autosave on or save the session before closing.

Yes, outermost window size is saved with session file, but zoom level is not. Yes, I no longer have to drag the window larger before zooming it, but I still have to zoom it ^3 every time. Please fix this!!

Ironic that recent "lawyer" change that forced user to "acknowledge" contents of system note before allowing him to do anything, is now nullified by making system note entirely unreadable without microscope. User is not even allowed to zoom the system note, he must first close it! :-/

On another note, I do appreciate the expandable log window columns finally. Thank you.

nichky · Thu Mar 12, 2020 4:43 am

*) added Legacy Mode = means to get access to device which have older version ROS version,is that correct?

anav · Thu Mar 12, 2020 5:48 am

I can confirm that when I rescale my display from extra large for my old eyes 200% down to teeny weeny 100% size, the log files do not overlap.
How do I get the log files to appear normal and maintain larger fonts sizes etc........ ????
I dont have this problem with other things like notepad++ for example!

Kindis · Thu Mar 12, 2020 10:49 am

All the issues I had with scaling is now gone as far as I know BUT i noticed something before. I run a 2 monitor setup with one 4K (laptop) and the other 1440 (external screen).
If I had the problem where I could not read the logs on either screens dragging the winbox window from one screen to the other and then back again would solve this issue for me.
When you do that Windows re-scales the window according to that screen and it made everything "readable" again on both screens.

conrad · Thu Mar 12, 2020 11:08 am

I confirm session windows inside main winbox windows are saved but their size seams to be restored to a kind of default preset size at each start

first start windows set up

on new session, also the same on winbox restart

I confirm it too

DenisPDA · Thu Mar 12, 2020 11:43 am

I confirm session windows inside main winbox windows are saved but their size seams to be restored to a kind of default preset size at each start

first start windows set up

on new session, also the same on winbox restart

Enable Autosave Session and check the Autosave on Close checkbox is checked.

Thu Mar 12, 2020 11:44 am

We have repeated the issue. It happens if Windows window scaling is used together with Winbox zoom. Autosave no longer works. We will try to fix it ASAP.

roe1974 · Thu Mar 12, 2020 11:49 am

We have repeated the issue. It happens if Windows window scaling is used together with Winbox zoom. Autosave no longer works. We will try to fix it ASAP.

thx a lot !

sid5632 · Thu Mar 12, 2020 12:17 pm

I'm still getting this flip-flopping of window sizes when starting winbox64.exe (on Wine under Linux Mint 19):

creating Window Class routeros_null
creating Window Class routeros_connect
DPI=100
EMS=13
ERROR: bad bmp format id=2329
biPlanes=1, biBitCount=1, biCompression=0
ERROR: bad bmp format id=3329
biPlanes=1, biBitCount=1, biCompression=0
creating Window Class routeros_dbl_canvas
 discovery started

then

creating Window Class routeros_dbl_canvas
DPI CHANGED to 120
rescale font 100 to 120
EMS=16
 discovery started

then

creating Window Class routeros_dbl_canvas
 discovery started

etc.

I also get the window pinned to 0,0 regardless.
Connecting to an actual router gives a window sized roughly 460x260 or 440x240 (depending on the above flip-flip).
This is worse than 3.21, which was itself bad. The last version that worked even vaguely properly was 3.20 (on Wine on Mint).

On Windows (7 - 64) it all seems to work properly for me, but I don't have any funky scaling settings.

mszru · Thu Mar 12, 2020 12:32 pm

Dear MT!

Would you consider changing the first column in the Log window to the running number?
Currently those numbers are from 0 to 999 and when the log is full (all 1000 lines populated) the specific log message will get a new number from the previous log entry with every new entry added. From my perspective the log entry number should start from 0 after a device reboots and should never be changed for a specific log message.

Does it make sense to you or anyone else here?
Thank you!

Sob · Thu Mar 12, 2020 2:59 pm

One cosmetic problem, optional fields have wrong vertical centering. With small zoom the text is too much to top, while with big zoom it's too much to bottom. It happens everywhere for this field type. Other fields (simple edits, dropdowns) have it correct.

tippenring · Thu Mar 12, 2020 3:27 pm

Dear MT!

Would you consider changing the first column in the Log window to the running number?
Currently those numbers are from 0 to 999 and when the log is full (all 1000 lines populated) the specific log message will get a new number from the previous log entry with every new entry added. From my perspective the log entry number should start from 0 after a device reboots and should never be changed for a specific log message.

Does it make sense to you or anyone else here?
Thank you!

I agree that the # column isn't necessary. The numbers are meaningless if they change which message they are associated with for every event. However, I do really like that I can select, open properties, and copy content from the log window now. Definitely need to keep that.

brotherdust · Thu Mar 12, 2020 8:35 pm

We have repeated the issue. It happens if Windows window scaling is used together with Winbox zoom. Autosave no longer works. We will try to fix it ASAP.

Normis, does this mean that Winbox will honor the scaling setting so that I don't have to zoom every time I open a new session?
Thanks!

Zwodka · Thu Mar 12, 2020 10:31 pm

I'm in love with new Log window

So am I

rushlife · Fri Mar 13, 2020 7:17 am

for what exactly ?
btw. still no native version for mac and linux, still no shortcuts implemented

,
otherwise - thanks for new version, is great, appreciated...

tpedko · Fri Mar 13, 2020 1:40 pm

add ctrl+c ctrl+v in the console

Sob · Fri Mar 13, 2020 2:31 pm

Ctrl+C already works for aborting commands. But it could probably have double use, where copying would work when there's some selected text. Or there are also safe non-conflicting Ctrl+Ins and Shift+Ins (my favourite, but those currently don't work in Terminal either).

Chupaka · Fri Mar 13, 2020 3:01 pm

Shift+Ins in Terminal works at least in Wine for MacOS.

Sob · Fri Mar 13, 2020 3:26 pm

Great, that's half of the work done. It would be real shame to not add Ctrl+Ins now.

pe1chl · Fri Mar 13, 2020 3:49 pm

I would still very much like to see the following changes:
- easier widget for selection of columns (a modal panel with checkmarks for all possible columns in a "square" layout where multiple checkmarks can be toggled before clicking OK)
- some way to raise windows that are covered by another window that has opened on top of it, e.g. a set of "window buttons" in the dashboard bar or some mouse action to "lower" the current window so other existing windows may appear on top of it.

pcunite · Fri Mar 13, 2020 11:37 pm

I would still very much like to see the following changes:
- easier widget for selection of columns (a modal panel with checkmarks for all possible columns in a "square" layout where multiple checkmarks can be toggled before clicking OK)

Agreed, takes way to much effort to deselect all the FP* columns, across multiple forms.

bda · Sat Mar 14, 2020 3:25 pm

Good day.
Some new bugs:

1. interface window resises to default size, even afer manual resize.
2. same for partition window.

pe1chl · Sat Mar 14, 2020 4:43 pm

Good day.
Some new bugs:

1. interface window resises to default size, even afer manual resize.
2. same for partition window.

Not here...

MTeeker · Sat Mar 14, 2020 10:58 pm

Good day.
Some new bugs:

1. interface window resises to default size, even afer manual resize.
2. same for partition window.

Same here. I experienced this resizing for the first time since switching to Winbox 3.22 (64 bit).

pe1chl · Sun Mar 15, 2020 1:38 pm

Moving items and changing column widths has become unstable!
When moving an item or changing a column width and keeping mouse button pressed for a while to find new suitable position, it suddenly jumps to completely wrong position.
I think this happens when the screen is updated in the meantime, e.g. to show updated counters in firewall view.

bda · Mon Mar 16, 2020 5:16 pm

Moving items and changing column widths has become unstable!
When moving an item or changing a column width and keeping mouse button pressed for a while to find new suitable position, it suddenly jumps to completely wrong position.
I think this happens when the screen is updated in the meantime, e.g. to show updated counters in firewall view.

Weird.... Plus auto windows resize...
I am waiting for a fix...

mpadmin · Mon Mar 16, 2020 6:45 pm

Good day.
Some new bugs:

1. interface window resises to default size, even afer manual resize.
2. same for partition window.

Same here on Windows 10. Also the last (and most important one) line of the log is very hard to read - it almost always stay "between" lines, auto scroll doesn't always work. I hope that bugfix version will be released.

brotherdust · Mon Mar 16, 2020 8:56 pm

Can I just make a suggestion here? Why not re-write Winbox with something like Qt framework? It has all this Hi-DPI nonsense already solved.. it's built in. Bonus: Winbox would become cross-platform! I guess it couldn't be called Winbox anymore, huh?

sid5632 · Tue Mar 17, 2020 12:53 pm

Also the last (and most important one) line of the log is very hard to read - it almost always stay "between" lines, auto scroll doesn't always work.

Yes, I'm seeing that too. Most irritating.

Abdock · Tue Mar 17, 2020 7:46 pm

how do i get winbox old version?

SiB · Tue Mar 17, 2020 9:21 pm

emils

What's new in v3.22:
*) added Legacy Mode (disabled by default) to allow using older, less secure connections to RouterOS older than v6.43;

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

.

*) added scroll bar support in item property windows;

It's still not that mouse scroll :(

Then what mean this point ??

Old bug with firewall chain's popup still exiting monitor

.

*) use monospace font for big pop-up messages;

It;s to big, but font it's now monospace like CLI, thanks!.

.

other

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

Tue Mar 17, 2020 10:40 pm

emils
What's new in v3.22:
*) added Legacy Mode (disabled by default) to allow using older, less secure connections to RouterOS older than v6.43;
I still must run WinBox 6.4 for manage old ROS v5.26 who cannot be upgraded to v6.x family.

What is WinBox 6.4?
Anyways, RouterOS 5 requires WinBox DLLs to be downloaded from the router. That was removed in WinBox 3.13 (and for a reason!) and has nothing to do with this "legacy connection mode".
By the way, what stops you from upgrading from RouterOS 5.x?

*) added scroll bar support in item property windows;
It's still not that mouse scroll
Then what mean this point ??

Property windows are not drop-down menus. Property window is what opens when you double-click on an item in the interface list, or a rule in the firewall rules window, etc.
And scroll bar is not a mouse wheel either!

owsugde · Wed Mar 18, 2020 1:08 pm

Looking good so far! 3.22 seems to be the version 3.21 was supposed to be. DPI problems all but vanished, as far as I've seen yet.

Add: Well except the fact that if you reconnect, the window is always reset as tiny size and everything is smashed together. That's not so great a thing.

Caci99 · Wed Mar 18, 2020 6:22 pm

Shift+Ins in Terminal works at least in Wine for MacOS.

One learns a new thing everyday. Thanks Chupaka for the tip

hngjared · Wed Mar 18, 2020 7:58 pm

Thank you for fixing log window!

owsugde · Thu Mar 19, 2020 10:48 am

The window size should be stored in session file. Make sure you have autosave on or save the session before closing.

It absolute does this, just not for all connections / remote devices. I wasn't able to isolate what actually causes this yet. Never happened before 3.22.

Please test around a little with this. It's a very annoying bug that wastes a lot of time and nerves.

Trezona · Sat Mar 21, 2020 4:35 pm

Where can i find the 3.21 version of winbox?

Sob · Sat Mar 21, 2020 6:43 pm

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe

w0lt · Sat Mar 21, 2020 6:59 pm

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe

T H A N K S

Trezona · Sat Mar 21, 2020 8:28 pm

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe

Thank you.

bda · Sun Mar 22, 2020 4:01 pm

Looking good so far! 3.22 seems to be the version 3.21 was supposed to be. DPI problems all but vanished, as far as I've seen yet.

Add: Well except the fact that if you reconnect, the window is always reset as tiny size and everything is smashed together. That's not so great a thing.

DPI problems are mostly here. If using 2k resolution with scale of 125-150 percents - all winbox windows and text looks weid.
Plus strange inner winbox windows resize bug.... Weird...

vv22 · Sun Mar 22, 2020 10:06 pm

Textbox with red text lost binding to the left side.
Winbox 3.22.

1.jpg

2.jpg

rushlife · Mon Mar 23, 2020 8:10 am

Hi to all of you, especialy MIkrotik team

.
I would be awesome use these quarantene days for making dedicated versions of winbox ( for linux / os x ).
Social distancing and lots of home office workers leads to make their working hours productive at least a little....

Chupaka · Tue Mar 24, 2020 2:41 pm

Social distancing and lots of home office workers leads to make their working hours productive at least a little....

What's non-productive in Wine?

rushlife · Tue Mar 24, 2020 5:38 pm

distorted fonts and slowness
don't even mention obligate to install bunch of software (over 1GB) because one small binary (about 2MB)

Chupaka · Tue Mar 24, 2020 10:18 pm

YMMV, but it works fast and smooth for me

ghostt · Wed Mar 25, 2020 9:38 am

Is the only problem the size? Are, for example, opened windows re-opened? Are you sure that you have launched WinBox loader with administrator privilegies, session is selected on WinBox loader before you access router (is not set to "<none>")?

Hello,
Yes, winbox is being launched with administrator privileges. What happens is this, all windows are opened, reopen on the next winbox session. But they are resized automatically if they are smaller then their some kind of default size.

For example. Even within one winbox session, If ip-addresses window is opened, resized to a small window, and closed, on re-opening it is bigger then it was set to. It's not a biggie, but could be quite annoying if you have a lot of windows opened and arranged on a screen, especially working from a laptop on a customer site.

Version 3.20 didn't have that issue. So far it's a decider for what I need, so rolling back to 3.20

Kind regards.

bda · Wed Mar 25, 2020 10:31 pm

Is the only problem the size? Are, for example, opened windows re-opened? Are you sure that you have launched WinBox loader with administrator privilegies, session is selected on WinBox loader before you access router (is not set to "<none>")?
Hello,
Yes, winbox is being launched with administrator privileges. What happens is this, all windows are opened, reopen on the next winbox session. But they are resized automatically if they are smaller then their some kind of default size.

For example. Even within one winbox session, If ip-addresses window is opened, resized to a small window, and closed, on re-opening it is bigger then it was set to. It's not a biggie, but could be quite annoying if you have a lot of windows opened and arranged on a screen, especially working from a laptop on a customer site.

Version 3.20 didn't have that issue. So far it's a decider for what I need, so rolling back to 3.20

Kind regards.

It is true. Same here. And weird artifacts on high DPI monitors with windows interface scaling. It is very bad!!!

Please, Mikrotik - do something!

robmaltsystems · Thu Mar 26, 2020 10:33 am

>added LegacyMode (disabled by default) to allow using older, less secure connections to RouterOS older than v6.43;

For the record, how has the security been improved in the later versions? Or maybe, why is the legacy mode insecure?

Thu Mar 26, 2020 10:49 am

Or maybe, why is the legacy mode insecure?

In legacy mode server identity validation is not implemented, thus making MITM attacks possible even if "Secure Mode" is enabled. The current implementation of the WinBox protocol was reported to use a flavor of SRP, so identity validation is now always mutual. Plus this "Secure Mode" can no longer be turned off.

freemannnn · Thu Mar 26, 2020 2:17 pm

when you hover over the "show columns" please make it not to have to click x times to reach what you want. just to scroll automatically.

pe1chl · Thu Mar 26, 2020 2:28 pm

when you hover over the "show columns" please make it not to have to click x times to reach what you want. just to scroll automatically.

This is why that long list should be replaced by a square input form with multiple columns of column names and associated checkmark...
Added advantage is that you can select all the columns you need in one go, so you don't have to open it 4 times to get rid of those 4 useless FP columns, for example (as you already did).

freemannnn · Thu Mar 26, 2020 2:45 pm

This is why that long list should be replaced by a square input form with multiple columns of column names and associated checkmark...
Added advantage is that you can select all the columns you need in one go, so you don't have to open it 4 times to get rid of those 4 useless FP columns, for example (as you already did).

i second this.

SiB · Thu Mar 26, 2020 3:12 pm

If not checkbox, then the CTRL + Click should on/off options.
Additional should be possible to use Mouse Scrool !.
I do that setup ones what is save in WinBox Session !. I have few sessions dedicate on differ platform/models.

pe1chl · Thu Mar 26, 2020 4:20 pm

i second this.

To answer your original remark: you can go to the end of the list by pressing the End key (and to the top by pressing the Home key).
But in remains a difficult UI.

SiB · Thu Mar 26, 2020 6:15 pm

pe1chl

To answer your original remark: you can go to the end of the list by pressing the End key (and to the top by pressing the Home key).
But in remains a difficult UI.

True.
In my Win10 the Home/End not work.
Only pressing letter few times do a skip by all that entry with that letter at start. Maybe in new WinBox...

pe1chl · Thu Mar 26, 2020 8:02 pm

Home/End has always worked for me, but I am only using winbox under wine (in Linux). Maybe the Home/End is a feature of wine rather than winbox?

raffav · Thu Mar 26, 2020 8:58 pm

I think the legacy mode msg it would be great if it tell you where to find it I.E Enable it on Tools, Legacy mode

DragosStanescu · Sun Mar 29, 2020 8:28 pm

Hey guys!
I have a problem connecting to a mAP Lite, it says: ERROR: router does not support secure connection, please enable Legacy Mode, if you want to connect anyway.
Does anybody know how to activate Legacy Mode, or bypass that error? I am using Winbox V3.22.
Thank you!

Sob · Sun Mar 29, 2020 8:46 pm

Tools->Legacy Mode

DragosStanescu · Sun Mar 29, 2020 11:00 pm

Thank you.

fengyuclub · Mon Mar 30, 2020 10:19 am

Snipaste_2020-03-30_15-12-42.jpg

Why the font of my winbox is different from yours, how can I use arial font, only the menu bar is arial font.

psannz · Mon Mar 30, 2020 10:47 am

If not checkbox, then the CTRL + Click should on/off options.
Additional should be possible to use Mouse Scrool !.
I do that setup ones what is save in WinBox Session !. I have few sessions dedicate on differ platform/models.

Yes! This. It would make life quiet a bit easier.

leonardovescovo · Mon Mar 30, 2020 4:03 pm

for what exactly ?
btw. still no native version for mac and linux, still no shortcuts implemented ,
otherwise - thanks for new version, is great, appreciated...

Native version for iPad too.

sev · Tue Mar 31, 2020 1:43 am

Gee, I thought I'm the only one loosing my mind with these windows resizing all over the place. But with same behavior on 3 win10 laptops I started googling - so hello erbody

Guess imma wait patiently for a fix tho. Peace

bda · Wed Apr 01, 2020 12:15 am

Gee, I thought I'm the only one loosing my mind with these windows resizing all over the place. But with same behavior on 3 win10 laptops I started googling - so hello erbody
Guess imma wait patiently for a fix tho. Peace

True, bro... Weird resizing too damn crazy!!! Peace too

Dear Mikrotik developers. Please, fix crazy resizing circus!!! Please!!!

bda · Thu Apr 02, 2020 5:57 pm

Sorry, but any news on fixing bugs with inner windows resizing?

pe1chl · Thu Apr 02, 2020 6:27 pm

I went back to 3.21
At first things looked bright but the problems with column resizing and row movement on busy windows like firewall filter are just too severe.

w0lt · Thu Apr 02, 2020 7:47 pm

I went back to 3.21
At first things looked bright but the problems with column resizing and row movement on busy windows like firewall filter are just too severe.

Ditto !!

conrad · Fri Apr 03, 2020 12:31 am

Dear Mikrotik developers. Please, fix crazy resizing circus!!! Please!!!

+

RogerWilco · Mon Apr 06, 2020 7:06 am

Coming up a month after 3.22 was released... any ETA on when the window resizing will be fixed. It is very annoying when you have a dozen windows open.

xsoft · Mon Apr 06, 2020 4:59 pm

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe

Thanks you.
After several test-cases I can confirm, that there is a but in 3.22 version when storing windows location/position/size to session file.
With 3.21 it works as designed (no bug).

Simple test case is to open 4 windows, resize them to smaller size, and layout all 4 fex px from each other.
Save and load session. 3.22 will NOT respect windows size/position, 3.21 will.
(winbox on fullscreen, windows 10)

bda · Tue Apr 07, 2020 12:11 am

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe
Thanks you.
After several test-cases I can confirm, that there is a but in 3.22 version when storing windows location/position/size to session file.
With 3.21 it works as designed (no bug).

Simple test case is to open 4 windows, resize them to smaller size, and layout all 4 fex px from each other.
Save and load session. 3.22 will NOT respect windows size/position, 3.21 will.
(winbox on fullscreen, windows 10)

Thanks! I think, that another bug is wrong size (and font font size) of main winbox window on hi res display with main OS interface resize to more than 100%, even 125% and winbox go crazy...

Kraken2k · Tue Apr 07, 2020 12:38 pm

Coming up a month after 3.22 was released... any ETA on when the window resizing will be fixed. It is very annoying when you have a dozen windows open.

yeah... every time you open the firewall rule edit window, it increases it's height until it fills the whole window. It drives my crazy after quite short time of work.

sterod · Tue Apr 07, 2020 6:29 pm

Coming up a month after 3.22 was released... any ETA on when the window resizing will be fixed. It is very annoying when you have a dozen windows open.

^- THIS!

dmitris · Tue Apr 07, 2020 11:52 pm

Hi all, i'm alone who have problem with winbox64 v3.22 and v3.21 on MacOS Catalina 10.15.4? To be precise i can't connect to any Mikrotik with latest ROS. Winbox window is splashing for a second and nothing happens. In Mikrotik log i see that user loged in and logout by winbox. Any ideas how to solve ?

btw.
Winbox64 3.20 works fine.

ghostt · Wed Apr 08, 2020 10:08 am

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe

Thank you!!!

ghostt · Wed Apr 08, 2020 10:13 am

@Trezona:
https://download.mikrotik.com/winbox/3.21/winbox.exe
https://download.mikrotik.com/winbox/3.21/winbox64.exe
Thanks you.
After several test-cases I can confirm, that there is a but in 3.22 version when storing windows location/position/size to session file.
With 3.21 it works as designed (no bug).

Simple test case is to open 4 windows, resize them to smaller size, and layout all 4 fex px from each other.
Save and load session. 3.22 will NOT respect windows size/position, 3.21 will.
(winbox on fullscreen, windows 10)

Windows version, full / windowed screen don't matter. I've tested that on multiple Windows machines (7, 7 Pro, 10, 10 Pro). The same thing is happening. Smaller the screen, more annoying the problem

RFS · Thu Apr 09, 2020 4:38 am

Здравствуйте! На моем нетбуке разрешение экрана 1024х600, и в Winbox внизу не видна кнопка "Connect" к WiFi, она просто не помещается. И прокрутки нет, и масштаб не изменить.
(Windows7x32)

Hello! My netbook has a screen resolution of 1024x600, and in the Winbox below the "Connect" button to WiFi is not visible, it just does not fit. And there is no scrolling, and the scale cannot be changed. (Google translate)

ghostt · Thu Apr 09, 2020 7:51 am

Здравствуйте! На моем нетбуке разрешение экрана 1024х600, и в Winbox внизу не видна кнопка "Connect" к WiFi, она просто не помещается. И прокрутки нет, и масштаб не изменить.
(Windows7x32)

Hello! My netbook has a screen resolution of 1024x600, and in the Winbox below the "Connect" button to WiFi is not visible, it just does not fit. And there is no scrolling, and the scale cannot be changed. (Google translate)

Привет! Попробуй предыдущие версии Winbox, 3.21 или 3.20

gemesif · Thu Apr 09, 2020 4:43 pm

Здравствуйте! На моем нетбуке разрешение экрана 1024х600, и в Winbox внизу не видна кнопка "Connect" к WiFi, она просто не помещается. И прокрутки нет, и масштаб не изменить.
(Windows7x32)

Hello! My netbook has a screen resolution of 1024x600, and in the Winbox below the "Connect" button to WiFi is not visible, it just does not fit. And there is no scrolling, and the scale cannot be changed. (Google translate)

I'm afraid, Winbox will not working good, in such low resolution...
May be solution the Webfig:

https://wiki.mikrotik.com/wiki/Manual:Webfig
by default:
http://192.168.88.1/

bda · Fri Apr 10, 2020 12:52 am

Coming up a month after 3.22 was released... any ETA on when the window resizing will be fixed. It is very annoying when you have a dozen windows open.
yeah... every time you open the firewall rule edit window, it increases it's height until it fills the whole window. It drives my crazy after quite short time of work.

Not only firewall, interfaces, but partitions, pools. And crazy inner window resizing!

kd2pm2 · Fri Apr 10, 2020 3:09 am

I have to believe that cloud backup will be part of winbox in the next release. Just a tad annoying to do it in the terminal

corp9592 · Wed Apr 15, 2020 2:54 pm

Oof... I believed that I was going crazy with the zooming issue.
I had to goo back to 3.20 to avoid any of the scaling issues. Thank God MT at least has older versions online, though it would not make any harm to make them available in the website under the Download Archive section.
As a software developer, I am starting to think that WinBox is becoming release after release a little bit more outdated. Sure it is not intended to have cutting edge UI/UX techniques, but the minimum UI tricks and perks, such as ctrl+scroll to zoom in/out, able to resize columns, resize subwindows using the secondary mouse button, sticky subwindows to allow "mosaics", ctrl-c, ctrl-v everywhere...

bda · Wed Apr 15, 2020 4:59 pm

Still waiting for new version.... But one good news - more and more CLI experience...

macsrwe · Wed Apr 15, 2020 8:55 pm

ctrl-c, ctrl-v everywhere...

+1.

I have never found a MikroTik user who found the current ^v "lock" feature useful. Conversely, I have assisted a number who were screaming "Jane! Stop this crazy thing!" after having activated it accidentally.

Maybe it's time to bite the bullet, discontinue it (or move it to control-altmode-cokebottle), and surrender ^c and ^v to the meaning they maintain in the entire rest of the universe.

jetelina · Thu Apr 16, 2020 12:35 am

After upgrading to 3.22 windows organization got little messy.
Top left corner of most of windows is on correct position, but width and height is not saved.
When window is on the bottom of screen, the default with and height is used and thus also top left corner is moved up.

ghostt · Thu Apr 16, 2020 2:36 am

ctrl-c, ctrl-v everywhere...

+1.

I have never found a MikroTik user who found the current ^v "lock" feature useful. Conversely, I have assisted a number who were screaming "Jane! Stop this crazy thing!" after having activated it accidentally.

Maybe it's time to bite the bullet, discontinue it (or move it to control-altmode-cokebottle), and surrender ^c and ^v to the meaning they maintain in the entire rest of the universe.

I agree 100%. Personally, constantly installing, configuring and maintaining Mikrotiks for many clients I have also never found current ^v feature useful, it's rather annoying I'd say. I do understand that Winbox developers may have 1000 reasons for their way of using ^v combination. But. At the end of the day, we are buying Mikrotiks and configuring them for our customers.

So, correct me if I'm wrong, it should be convenient to use Winbox for people "in the field". I'm trying to say that developers should listen a little bit more to our feedback than to "people in the laboratories where everything is working".

tommyd · Fri Apr 17, 2020 11:50 am

*) fixed Zoom In/Zoom Out setting persistence after window is closed;

Sorry to say but this is a dumpster fire. Windbox does no remember correctly the zoom level, it seems it zooms out with every reopen of the session session, messes up windows size and position even when saving session to file.
Please also add Ctrl-mouse wheel support for zoom

emils · Fri Apr 17, 2020 3:24 pm

Winbox v3.23 has been released:

viewtopic.php?f=21&t=160050

Who is online