Codemark news
Codemark BETA-0.2.0 veröffentlicht
2026-06-05 13:02:31
Changelog
Changed For Users
- The app has been renamed from LogiQR to Codemark.
- The app now uses the new Codemark logo, icons, app name, update names, export names, setup texts, and updater texts.
- Codemark is now presented as an app by Qubik Studios.
- The app header now shows the Codemark logo instead of a plain text title.
- The logo adapts to light and dark themes.
- The About/settings area now shows updated Codemark and publisher information.
- The default example QR content is now
Codemark. - The website button is disabled when no official website URL is configured.
Performance And Responsiveness
- Codemark now uses C optimization for better runtime performance across Windows, macOS, and Linux.
- QR previews are cached so repeated changes and window resizing feel smoother.
- Preset thumbnails are cached and generated more efficiently.
- Heavier export work runs in the background so the interface stays more responsive.
- Visual effects and animations were adjusted to reduce unnecessary load in packaged app versions.
- Background animations pause or reduce work when the app is minimized or moved.
QR Creation And Export
- All QR content types from the first public beta remain available, including links, plain text, contacts, WiFi, e-mail, phone, SMS, and location data.
- Logo handling is more flexible and scan-friendly.
- Logos can use improved sizing, padding, background, rounded background, border width, and border color options.
- Transparent logo edges are handled more cleanly.
- PNG and SVG exports stay closer to the live preview.
- Export now runs a QR self-test before writing risky output.
- QR quality checks cover readability, contrast, quiet zone, rotation, reflection, degradation, and optional decoder validation when OpenCV and NumPy are available.
- Auto-fix can apply safer QR settings after a failed scan test.
Presets And Session Recovery
- Existing LogiQR presets and session data can be copied into the Codemark app directory on first run.
- Autosave avoids unnecessary rewrites when nothing important changed.
- Codemark can offer to restore the last autosaved custom preset after an unclean shutdown.
- Older preference data is handled more tolerantly during the move to Codemark.
Updates
- Update checks now use the Codemark app identity.
- Codemark checks for updates silently after startup and through passive background checks.
- When an update is available, the app shows an in-app update banner.
- Repeated update checks are paused while an update is already available.
- Downloaded updates are checksum-verified before installation.
- Packaged Windows installations can hand off verified updates to the Codemark updater.
Setup And Updater
- The setup wizard now uses Codemark wording throughout the install, update, repair, uninstall, and launch flow.
- Setup verifies that both the main app and updater are installed correctly.
- Setup validates downloaded packages before installation.
- Setup now expects the install folder to be named
Codemark. - Legacy LogiQR shortcuts can be cleaned up during uninstall.
- The updater waits for the running app to close before replacing files.
- The updater creates a backup before replacing the app executable and can restore it if replacement fails.
- The updater can restart Codemark after a successful update.
Sponsor Slot
- Sponsor content now uses the Codemark app identity.
- Sponsor content can be selected from multiple available entries.
- Sponsor data is cached so the app does not need to request the same content repeatedly.
- Sponsor images are loaded more defensively and reused while cached data is valid.
Debug And Developer Notes
- Development versions now use Codemark-branded debug output.
- Debug tools remain disabled automatically in release-like packaged app versions.
- A developer-only layout overlay was added for UI tuning.
Compatibility Notes
- Existing LogiQR user data can be copied into the Codemark app directory on first run.
- Legacy LogiQR folders are not deleted automatically.
- Users moving from LogiQR should verify that presets and session data were copied correctly.
- Exported QR codes should still be tested before production print use.