| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| MoTekLab-Proxy-Suite-1.7.0.AppImage | 2026-05-10 | 166.6 MB | |
| MoTekLab-Proxy-Suite-1.7.0.tar.gz | 2026-05-10 | 152.1 MB | |
| MoTekLab-Proxy-Suite_1.7.0_amd64.deb | 2026-05-10 | 99.3 MB | |
| README.md | 2026-05-10 | 2.7 kB | |
| Totals: 4 Items | 418.0 MB | 0 | |
[1.7.0] - 2026-05-10
Changed
- Keyboard reset uses GDK
setEnabled+ X11setFocusabletoggle with yield instead of blur/focus — replaced the oldsetFocusable(false)+blur()+setFocusable(true)+focus()sequence (which changed window Z‑order) withsetEnabled(false)+setFocusable(false)→setImmediateyield →setFocusable(true)+setEnabled(true)+webContents.focus(). Disables both GTK sensitivity (GDK) and WM_HINTS.input (X11), lets GLib process both disconnections, then re-enables and forces Chromium to register fresh keyboard signal handlers. Z‑order impact: none — the window stays in place. - Batch SQLite operations broken into 100-item chunks with
setImmediateyields —performBatchOperationfordelete,updateStatus,updateProtocol, andchecknow processes proxies in batches of 100, yielding to the event loop between each batch viasetImmediate. - Proxy checker yields to full event loop between batches — replaced
await this.delay(20)withawait new Promise(resolve => setImmediate(resolve))inprocessQueue().
Added
- Concurrency slider for Proxy Checker —
check.concurrentsetting is now rendered as a<input type="range">slider (range 5–200, step 5). Concurrency is read from settings when a batch check starts. - Automatic keyboard reset restored — since
setEnabled+setFocusabletoggle has no Z‑order impact, keyboard reset is called automatically after proxy check completion and batch database operations.
Fixed
- Permanent keyboard freeze triggered by "Cleanup Dead" (batch delete) on Linux — root cause identified as GLib-GObject IME signal handler disconnect (
gsignal.c:2685: instance has no handler with id). Three-pronged fix: - Removed
confirm()dialogs fromhandleCleanDeadandhandleCleanByLatency— the Chromium modal dialog generated focus events that triggered internal IME teardown IPC, which disconnected the GLib keyboard signal handlers. - Switched
db:batchIPC frominvoke/handletosend/on—ipcRenderer.invoke()uses the Mojo synchronous IPC path which corrupts GLib state during dispatch.ipcRenderer.send()uses the message path which avoids this. - Added
setImmediateyield at start of batch IPC handler — gives GLib time to settle any pending IME/focus events before our handler runs. confirm()dialogs removed from batch delete operations — deleting dead/slow/filtered proxies no longer shows a confirmation dialog, preventing the focus-change→IME-teardown→GLib-corruption sequence. The notification toast on completion provides sufficient feedback.