WD Wireless Tools v2.246.16

Cloud Manager: a comparison names which copy each difference is on and which is newer

Suite 2.246.16, Cloud Manager 4.93.0.

What changed

Cloud Manager (Projects tab, "Check what differs")

• Every count in the "Real changes" line now names its side. The line used "added" and "removed", which did not say whether the item was in the cloud copy or in the local file. It now reads, for example, "Real changes: access points (3 changed, 1 only in cloud, 2 only in local)". "Only in cloud" means the cloud copy has the item and the local file does not; "only in local" means the reverse; "changed" means both have it and it differs.
• The line also says which copy has the later date. After a comparison that finds real changes, the row adds "The cloud copy has the later date." or "Your local file has the later date.", so the side to keep can be chosen from the row. Before, the later-date sentence disappeared as soon as a comparison had been run.
• The "What differs" list under the line already used "only in local" and "only in cloud" and is unchanged.

Verified

• Tests compare two archives with a different access point on each side and check that each count appears under the correct side, and that "added" and "removed" no longer appear.
• A test renders the row for a comparison with real changes and checks that the correct "later date" sentence is present and the other is not. Both tests fail with the change reverted.
• The full suite passes.

Files changed

• tools/esx_compare.py
• web/assets/js/cloud.js
• tests/test_esx_compare.py
• tests/test_cloud_compare_says_what_differs.py
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.14

Prep and Capacity: Undo last corner while drawing a requirement area

Suite 2.246.14, Prep 2.10.0, Capacity 1.13.0.

What changed

Prep (Requirement areas) and Capacity (Draw the area)

• A new "Undo last corner" button takes back the last corner clicked while drawing a shape. It sits between "Draw a shape" and "Back to automatic" in the "Draw the area" panel. Each press removes one corner, so a mis-click partway through a long outline no longer means starting again. The button is greyed out until a shape is being drawn and at least one corner has been placed; taking every corner back leaves "Draw a shape" active so drawing can continue.
• Ctrl+Z (Cmd+Z on a Mac) does the same. Backspace and Delete continue to work as before.
• The line under the buttons counts the corners placed while a shape is being drawn, for example "Click each corner (5 so far)", and names the three ways to take one back.
• A corner placed again on the spot just taken back is now treated as a new corner. Previously a click on the same spot straight after an undo could be read as a double-click and finish the shape early.
• "Draw a rectangle" is unchanged: a rectangle is one drag, and Esc still cancels it.

Verified

• Tests drive the editor with real mouse and keyboard events on a real plan view and check the corners that arrive: one corner removed per press, nothing removed when none are placed or when no shape is being drawn, Ctrl+Z and Cmd+Z undo while Shift+Ctrl+Z does not, a corner clicked after an undo lands where it was clicked, and the buttons and the corner count follow each click and each undo. The button's handler is taken from the rendered markup and run. Each check fails when the matching behaviour is removed.
• The full suite passes.

Files changed

• web/assets/js/wd-areaeditor.js
• tests/test_area_editor.py
• docs/USER_MANUAL.md
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.13

AP Labeler: a Simulated name left behind is reported, and unnumbered APs are easy to spot in Manual order

Suite 2.246.13, AP Labeler 2.22.0.

What changed

AP Labeler (naming and download)

• An AP that would still be named "Simulated …" is reported. Ekahau gives a newly placed AP a name such as Simulated AP-47. When any AP on a floor being renamed would still carry one, an amber note under "Preview" gives the count and lists every such AP by floor. The floor name in the note opens that floor. The note updates as numbers are assigned and disappears when none are left.
• "Download labeled .esx" asks first when any are left. The question names each AP (up to twelve; past that, the count per floor, with every name listed under "Preview"). "OK" downloads the file as it is; "Cancel" returns to the plan without building anything. Floors excluded under "Floors to rename" and names the pattern writes itself, such as AP-001, are not reported.

AP Labeler (Manual order)

• APs still to be numbered are drawn as large white discs with a thick ring in the AP's own colour, edged dark inside and out. The previous marker was a small disc with a thin dashed ring, which was easy to lose on a busy plan, and a pale colour such as yellow was hard to see on white paper. A numbered AP remains a smaller disc filled with its colour and showing its number, so the ringed discs are the ones left to do.
• Clicking an AP that already has a number now says so. A click on a numbered AP has always removed its number and moved the later ones down. A message now names the number removed and the AP, and says that "Undo" puts it back. Going over a floor a second time by clicking each AP removes each number in turn, so redoing a floor is done with "Clear floor".
• The counter beside "Next" shows the floor on screen first. It reads, for example, 2 of 19 on this floor · 22 of 39 numbered in all. Before, it showed only the whole-project figure. On the "Unplaced" tab it shows the whole-project figure only.
• User manual: the "Manual (click order)" and "Download" sections describe the markers, the counter, and the Simulated report.

Verified

• Tests drive the real handlers: the report lists exactly the Simulated names, per floor, redraws as numbers are assigned, opens the right floor from its button, and Download asks and builds nothing on "Cancel". Each of these fails when its behaviour is removed.
• A browser test in Chrome, Edge and Firefox measures the markers: an unnumbered AP is larger than a numbered one, its ring is at least 4 pixels, it is white inside and edged dark, and a yellow ring keeps those edges. It fails with the previous marker size.
• The full suite passes.

Files changed

• web/assets/js/ap-rename.js
• web/ap-rename.html
• web/assets/wd-tools.css
• tests/test_ap_labeler_numbers_what_it_shows.py
• tests/test_ap_labeler_manual_markers_browser.py
• tests/test_the_stylesheet_stays_on_its_scale.py
• docs/USER_MANUAL.md
• web/assets/versions.json
• README.md
• docs/releases/v2.246.13.md

WD Wireless Tools v2.246.12

Report: the grid dialogs list floors down the left

Suite 2.246.12, Report 2.77.0.

What changed

Report (Configure step)

• Configure grid… lists the floors down the left of the dialog. Each floor is a button showing its name and the number of APs on it; the floor being edited is highlighted. Clicking a floor switches to it, with that floor's crop and combined sections as they were. This replaces the Floor plan dropdown above the plan.
• Set up column grid… does the same. A tick beside a floor means its column grid is saved. The tick appears after Save this floor and goes after Turn off for this floor.
• With more than 20 floors the dropdown is used instead. A report covering 21 or more floors shows the Floor plan dropdown in both dialogs, as before, rather than a long list. Up to 20 floors are listed; the list scrolls inside the left column.
• Only the floors in the report are listed, the same set the dropdown offered: floors unticked under Floors to include are not shown.
• The tick in the column-grid dropdown now clears when a floor is turned off. Previously it stayed until the dialog was reopened.
• The step text in Configure grid… and the User Manual now describe the list and the 20-floor limit.

Verified

• Tests render both dialogs from an invented three-floor project, take the click handler out of the rendered list, run it and check that the dialog moves to the chosen floor and the highlight follows. They check that a floor left out of the report is not listed, that the tick follows the saved column grids, and that 20 floors give the list while 21 give the dropdown. Each fails when the 20-floor limit is changed or the click no longer switches floors.
• The dialog was checked visually in light and dark themes with twelve floors: the list sits in the left column, the current floor is highlighted in Report's colour, the list scrolls within the column, and the dropdown is hidden.
• The full suite passes.

Files changed

• web/report.html
• web/assets/js/report.js
• web/assets/wd-tools.css
• docs/USER_MANUAL.md
• tests/test_report_floor_selection.py
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.10

Squirrel: the preview lists only what will move, and nothing shows above its header

Suite 2.246.10, Squirrel 1.31.0.

What changed

Squirrel (Organize Files preview)

• The list can show only the site folders that have files to move. After a folder is scanned and Show File Details is pressed, a Show control on the row with Check All, Uncheck All, Advanced and Apply Moves has two buttons: Moving only and Everything. Moving only is the default. It lists just the site folders with files to move, without the "Staying in root" tables, so a large folder no longer has to be scrolled to find the files the summary counts. A note beside the buttons says how many site folders are hidden. Everything lists every site folder and the files that stay, as before.
• The choice is remembered and survives rescanning. Switching between the two does not redraw the list, so a file that was unchecked or given a different destination keeps that setting.
• With Advanced on, a site folder with unreferenced images or floor plans stays in the list under Moving only, even when nothing in it will move.
• If nothing will move, Moving only says so and points to Everything.
• Rows no longer show above the header while scrolling. The bar with Change Folder, New Folder, Rescan and Settings, and the summary below it, now hold at the very top of the scroll area. Previously a strip of the list's top margin stayed above the bar, and file rows scrolled up through it.

Verified

• A browser test in Firefox, Chrome and Edge scans an invented folder of forty sites with three files to move. It checks that the list opens on the two sites with moves, that Everything lists all forty, that an unchecked box stays unchecked after switching back and forth, that the choice survives a rescan, and that after scrolling the element at every point along the top edge of the list is the header. It fails when the hiding rule is removed and when the header is held at its old position.
• The full suite passes.

Files changed

• web/organizer.html
• web/assets/js/organizer.js
• web/assets/wd-tools.css
• web/assets/settings-registry.json
• docs/USER_MANUAL.md
• tests/test_squirrel_preview_stays_readable_browser.py
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.9

Squirrel: the Select Folder button lines up with the other cards' buttons

Suite 2.246.9, Squirrel 1.30.2.

What changed

Squirrel (opening screen)

• The "Select Folder…" button on the Organize Files card is on the same line as the buttons on the other four cards. When a previously used folder was remembered, the "Last:" line and the "or continue with this folder" link were shown below the button, which pushed it higher than the rest. They are now shown above the button, between the card's description and the button, so the buttons stay level whether or not a folder is remembered.

Verified

• A browser test with the remembered-folder line showing checks that the line sits above the button and that all five buttons end at the same height. It fails with the previous layout, where the Organize Files button ended about 100 pixels higher than the others.
• The full suite passes.

Files changed

• web/organizer.html
• web/assets/wd-tools.css
• tests/test_squirrel_home_fits_the_screen.py
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.8

Launcher: the Windows Terminal tab now opens reliably, and a failure no longer closes the launcher silently

Suite 2.246.8. Tool versions are unchanged.

What changed

Start WD Wireless Tools (Start WD Wireless Tools.bat, Windows)

• The launcher joins an open Windows Terminal window, or opens a new one when none is open. It checks whether Windows Terminal is running first. Previously it always asked for "the most recent window", and after a Windows Terminal window had been closed that request could be accepted without opening anything, so the launcher's own window closed and the app never started.
• The launcher confirms the tab opened. The new tab reports back as soon as it starts. If nothing reports within 15 seconds, the other window choice is tried once, and if that also fails the launcher runs in the window it was started from and prints why. It no longer closes its window on the strength of a tab that never appeared.
• A restart from inside the app uses the same check, so a restart that cannot open its tab falls back to the previous restart behaviour instead of leaving no app running.

The "Open in a Windows Terminal tab" option under Settings, General is unchanged. When it is off, or Windows Terminal is not installed, the launcher runs in its own window as before.

Verified

• A double-click through Explorer was run in both cases: with no Windows Terminal running (a new window opened and the app answered on its port) and with one already open (the existing window was reused, with a single Windows Terminal process afterwards).
• New tests cover the window choice, the confirmation, both fallbacks, the timeout, a stale confirmation left by an earlier run, and the batch file's report from inside the tab. Each fails when the corresponding behaviour is removed.
• The full suite passes.

Files changed

• tools/terminal_tab.py
• Start WD Wireless Tools.bat
• tests/test_terminal_tab.py
• tests/test_launchers_check_dependency_versions.py
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.7

Launchers: the start file now upgrades packages that are out of date

Suite 2.246.7. Tool versions are unchanged.

What changed

Start WD Wireless Tools (Start WD Wireless Tools.bat on Windows, Start WD Wireless Tools.command on macOS)

• Out-of-date Python packages are upgraded at launch. The start file used to check only that the packages could be imported, so a package that was installed long ago and still imported was never looked at. It now compares each installed package with the minimum version in requirements.txt and, when one is missing or older, runs pip install --upgrade -r requirements.txt before the app starts. Pillow is the package where this matters most: it decodes the floor-plan images inside .esx files.
• A failed upgrade does not block the launch when everything is installed. If every package is present but one is older than its minimum and the upgrade cannot run (for example, no network), the start file prints a warning and starts with the versions installed. A missing package still stops the launch with the install command to run by hand.
• The macOS start file now also covers Pillow, which its old check left out.

Dependency check (python -m tools.deps)

• The exit code now says which case applies: 0 all current, 1 something missing, 2 everything installed but something older than its minimum. The installers still treat any non-zero code as "update".

Verified

• A new test runs the dependency step of each start file against a stand-in Python and checks the four outcomes: current (pip not run), missing or older with a successful upgrade, older with a failed upgrade (launch continues), and missing with a failed install (launch stops). It fails when the upgrade flag or the continue-on-older branch is removed.
• The full suite passes.

Files changed

• Start WD Wireless Tools.bat
• Start WD Wireless Tools.command
• tools/deps.py
• tests/test_launchers_check_dependency_versions.py
• web/assets/versions.json
• README.md

WD Wireless Tools v2.246.6

Settings: the panel no longer has empty margins either side

Suite 2.246.6. Tool versions are unchanged.

What changed

Settings (the panel over Home or over any tool)

• The content fills the panel from edge to edge. In 2.246.5 the panel was 1480px wide while the content inside it stopped at 1200px, so on a wide screen there was an empty band of about 150px on the left and on the right. The panel is now 1280px wide and the content fills it, so nothing is left over.
• The Settings page on its own is capped at the same 1280px, so it and the panel match. The panel is still wider than the 860px it was before 2.246.5.

Verified

• The panel was opened from Home in the browser's built-in Chromium engine at a 1900px-wide window: the cards start at the panel's left edge and the settings box ends at its right edge.
• A new browser test, run in Firefox, Chrome and Edge in CI, opens the panel at a wide window size and fails if the cards, the title or the settings box sit more than 48px in from either edge. Before the change it measured 152 to 167px on both sides in all three browsers.
• The full suite passes.

Files changed

• web/assets/wd-tools.css
• web/assets/versions.json
• README.md
• tests/test_settings_frame_holds_still_browser.py
• tests/test_settings_page_is_usable.py

WD Wireless Tools v2.246.5

Settings: a title for the open section, a wider window, and nothing that jumps

Suite 2.246.5. Tool versions are unchanged.

What changed

Settings (the panel over Home or over any tool, and the page at Menu → Suite Settings)

• The open section has a title across the top of its box. It reads "Cloud Manager", "Report" and so on, on a band in that tool's colour with a line under it. Before, only the highlighted card said which section was showing.
• Nothing moves when a section is chosen. The page title, the cards, the box the settings sit in and the Save and Cancel buttons stay exactly where they are for all nine sections. Only the settings scroll, inside the box. Before, the whole window scrolled with the length of the section, so the title left the top, a short section picked after a long one could be left scrolled out of view, and the buttons shrank on the two sections with nothing to save.
• The Settings window is wider, up to 1480px and 94% of the window's height, instead of 1240px and 92%.
• The card list no longer grows a scrollbar of its own on a short window. Below about 880px of height the cards tighten and show their description on one line, so all nine fit beside the box.
• Windows narrower than 561px keep the stacked layout, with the cards in a grid above the section and the page scrolling as a whole.

Verified

• The real Settings panel was opened from Home in the browser's built-in Chromium engine, and each of the nine sections was chosen in turn. The page title, cards, box, title band and buttons measured identical for all nine, the page did not scroll, and scrolling the box brought the last settings of Cloud Manager into view.
• A new browser test, run in Firefox, Chrome and Edge in CI, chooses each section and checks that nothing moves, that the title names the card pressed, and that the end of every section can be reached with the mouse wheel. Undoing any part of the layout turns it red.
• The full suite passes.

Files changed

• web/assets/wd-tools.css
• web/assets/versions.json
• README.md
• tests/test_settings_frame_holds_still_browser.py
• tests/test_settings_page_is_usable.py