Repository navigation
Fast on large projects, and failures you can see.
On a large design, the Optical Schematic View, the list of latent elements, the route correction check, Generate terminal slacks, placing a slack, FiberQ's own snapping in the placement tools, the undo record after every placement and Lay cable used to scan every feature. They now use spatial indexes and batched reads instead. And the operations that save, export, import or migrate data now say when they fail, and why, instead of failing silently or reporting success.
Faster on large projects
On a generated test city of 88,622 features, QGIS 3.44, median of the timed runs:
| What you do | 1.5.0 | 1.6.0 |
|---|---|---|
| Open the Optical Schematic View | 16 min 39 s | 11.3 s |
| Open the list of latent elements | did not finish in 30 min | 5.04 s |
| Route correction (the check), with 1.5.0's findings | 3 min 22 s | 1.36 s |
| Generate terminal slacks for 50 cables | 42.5 s | 398 ms |
| Place one slack | 694 ms | 155 ms |
| Nine mouse moves with the route tool | 4.52 s | 35.8 ms |
| FiberQ's undo record after a placement | 57.2 ms | 6.52 ms |
| Lay one cable | 1.06 s | 471 ms |
Every figure, at three sizes and on QGIS 3.44 (Qt5) and 4.0 (Qt6), is in docs/performance.md, with the method, the raw result files and the limits. By its rule, nothing is measurably slower than in 1.5.0. Two slowdowns fall outside the rule, and the page states both. On memory layers (a project that has not been saved yet), each of the three placement tools measured pays about 0.06–0.10 ms more per mouse move, and the joint-closure tool stays that much slower at every size. In a fresh QGIS, the joint-closure tool's first moves are slower than 1.5.0's in four of the five tables.
Failures you can see
- One message per failed operation, with the reason; the details are in Log Messages > FiberQ. Save all layers to GeoPackage and Auto-save name the layers that did not save. Export layer, the BOM export, Import points, Import route, Merge routes, Change route type, Change element type, Delete selected, Undo and Redo, and Lay cable check their writes and report a failure instead of a success message.
- The project's own data is not lost unseen. When FiberQ cannot read the relations, latent elements or colour catalogues stored in a project, it says so and copies the unreadable text to a separate entry in the project, so a later save cannot lose it.
- Unhandled Python errors fixed: route correction (a pole without a geometry, a multipart route, a raster layer in the project), the Optical Schematic View's Center button, Import route on point or empty geometry, Import points and Import route on a coordinate that cannot be transformed, the BOM export to a locked or read-only file, and the slack tools on a pre-1.0 project. On QGIS 4, clicking an element with a picture now opens the picture.
- A test stops silent error handlers from growing back. The hardening covers the operations that write, export, import or migrate data, not every error handler in the plugin.
Also in this release
Lengths follow your edits. The placement tools follow QGIS's snapping settings and show its snap indicator. Validation settings are stored in the project. Save all layers keeps the metadata other tools stored in the file. Publish to PostGIS reports a failed export and refuses a table name already in use. Picture and drawing links survive saving in QGIS 3. An interchange bundle import never replaces what the project already has, and an export refuses or warns instead of writing something other than the project. The plugin loads on QGIS 3.22 again. The full list, with every behaviour change, is in the changelog (Plugins > Manage and Install Plugins > FiberQ).
Changed: the "Check (health check)" button is gone (Validate project covers it). The BOM measures lengths on the ground, so its figures differ from 1.5.0's. Merge routes, Change route type, Change element type, Lay cable and Undo no longer save your other unsaved edits. Save all layers to GeoPackage, and turning Auto-save on, ask before writing over a table of the same name that no layer of the project uses. Route correction's Correct moves a route end only onto the nearest pole, manhole, joint closure or element within 5 m.
Quality
- Clean plugins.qgis.org Security & Quality scan (flake8 + Bandit 0/0).
- The full test suite is green on five QGIS versions: 3.22 (the declared floor), 3.40 LTR, 3.44, 4.0 and 4.2, 2,275 to 2,308 tests each, Qt5 and Qt6.
- Tested by hand in QGIS 4.2 and 3.40 with the 1.6.0 re-check list. Its tests 19–31 were also replayed click by click in QGIS 4.2.3 and 3.40.15 on the release's plugin folder: 589 of 589 checks came out as the list expects.
Targets QGIS 3.22 LTR → QGIS 4 / Qt6.
The spatial indexing and batching behind the speed-ups, their benchmark, the failure reporting and the crash fixes were developed with support from the NLnet NGI0 Commons Fund. Everything else in this release, including the fixes made during its release testing, was not funded by it.
If FiberQ saves you time, you can help fund its development: GitHub Sponsors · other ways to give.