ZOVANTA SOFTWARE / KNOWLEDGEBASE

Tabvanta 0.1.0-alpha59 • Windows alpha source

Diagnose the broker and native-dialog flash

Start with the running build

Exit the existing broker through its tray menu, launch alpha59, and save the integration settings. If an older broker cannot release control, inspect its process path before testing. Avoid testing an old installed broker while assuming the new debug window controls interception.

Collect logs

Open %LOCALAPPDATA%\Tabvanta\startup.log. Alpha59 records DialogStart, Create and Show hook handles. If a hook is 0x0, retain the newest lines and the executable path for support. The updater has a separate %LOCALAPPDATA%\Tabvanta\logs\update.log.

Repeatable checks

  1. Keep Task Manager open and start with only the tray broker running.
  2. Open Notepad → File → Open, then Save As. Note whether the native dialog flashes once or repeatedly.
  3. Test a folder picker and a browser/PDF Save As operation.
  4. Verify ordinary message boxes, Explorer, taskbar, menus, volume overlay and notifications remain normal.
  5. Cancel and close the picker; confirm the original operation ends and no late picker appears.
  6. Switch to another application and check that Tabvanta does not cover it globally.

Recovery

If interception loops or a picker fails, the source includes a circuit breaker and two-second render watchdog intended to restore the native operation. Stop automatic integration if your application remains unstable and use its native picker. Report the calling application's name/version, Tabvanta executable path, operation and redacted startup log.

The supplied source handoff leaves Windows acceptance tests open. A previous user test still observed an initial native-dialog flash. This documentation update does not mark that issue resolved.