Skip to content

ELKA EventLens 0.1.0-dev.4 - Development Preview

Pre-release
Pre-release

Choose a tag to compare

View all tags
@torment78 torment78 released this 20 Oct 04:23
v0.1.0-dev.4
1496d50

ELKA EventLens 0.1.0-dev.4

Development preview for testing, not a stable release.

Upgrade and Storage Fixes

  • Setup now replaces the registered old Elka Software\ELKA EventLens installation under C:\Program Files\ElkaSoft\ELKA EventLens, even when Setup remembered the old folder or an older updater supplies it. Custom installation folders are preserved.
  • The old uninstaller removes its own program files. Other applications and unknown files are not recursively deleted. Exit EventLens from the tray before a manual upgrade; running old copies block removal.
  • Existing saves, history, logs, and the browser profile move into the ElkaSoft data layout. After successful startup, leftover legacy data moves intact into timestamped LegacyRecovery folders, without overwriting current data. Empty old folders are removed.
  • Cleanup failures retain the source and retry on a later launch. Portable storage remains beside the executable and never migrates installed data.

Downloads

Use ELKA_EventLens_Setup_0.1.0-dev.4.exe for installed copies or ELKA_EventLens_Portable_0.1.0-dev.4.zip for portable copies. SHA-256 checksums are in SHA256SUMS-0.1.0-dev.4.txt. Preview executables remain unsigned; Windows may show a warning.

The normal installer location is C:\Program Files\ElkaSoft\ELKA EventLens. Saves are in %AppData%\ElkaSoft\ELKA EventLens\Saves; browser data and logs use the corresponding %LocalAppData% app folder. Website sessions may still expire or require login.

Verification

All 125 app checks passed, including migration, recovery, retry, junction protection, updater behavior, layout, and embedded browsing. Four isolated installer scenarios passed: remembered old path, older updater path plus restart, running-old-app protection, and custom-directory preservation. The portable archive was checked for runtime files and exclusion of private data; both package checksums were verified.

Tests use synthetic saved data and a separate installer identity, not the real installed app. Production UAC approval and real third-party login sessions remain user acceptance checks.

Assets 5
Loading