What's new in mlinstall 1.1.0
Jan 16, 2024
- New Functionality (all platforms):
- Shutter count is now displayed once connected
- Internal build version is displayed once connected
- mlinstall can be invoked with CLI to upload files with CHDK PTP
- Binary changes:
- Windows app is now a single .exe (around 30x smaller)
- UI Changes:
- UI is now based on libui-ng
- Added 'Connect to camera' button which enables the rest of the USB tab
- A lot of wording improvements
- Changed the layout of the logs/tabs
New in mlinstall 1.0.0 (Apr 17, 2023)
- Deleted the forked libptp backend (70% of the codebase) and replaced it with camlib
- camlib is a new PTP library written from scratch. It's currently being used in commercial software and works well.
- Removed the 'module store' (cool gimmick, wasn't useful)
- Unlike libptp, camlib has native support for Windows through libwpd. This means that all the libusb-win32/zadig/driver corruption nonsense is over now.
- camlib has been tested and works on MacOS, so porting it might be a case of tweaking the makefile.
New in mlinstall 0.9.3 (Dec 14, 2022)
- I'm now discouraging all use of Zadig, the tool I previously recommended to install LibUSB win32 on Windows systems. This release includes a copy of the libusb filter installer (install-filter-win.exe) which is straightforward to use, and is much less intrusive than Zadig.
New in mlinstall 0.9.2 (Aug 7, 2022)
- Next release will hopefully be the same as this. If any bugs are detected after this release, they will be fixed before 1.0.0.
- A copy of Zadig is now included in the windows ZIP.
- Tweaked some text
New in mlinstall 0.8 Early Release (Oct 30, 2021)
- Updated Windows drive code, hopefully is much more reliable and safer
- Added .lua scripts in app store
- Removed evproc parameters, doesn't seem to work
- Move warning to console output, more confident that it won't break
New in mlinstall 0.7 Early Release (Oct 4, 2021)
- Added a Module "App Store". You can plug in your SD Card and download modules. See #5
- Added "Activate evproc execution" button as per Ant123's findings
- Fixed EXFAT detection bug, still not supporting ExFAT, see #4
- Fixed drive detection string bug
- Etc bugs