MangAI v1.02a released
New to version 1.02a:
-Bug fix: Potential freeze during Manga Scan Model scan analysis
Bug was introduced in v1.02 and allowed for a potential infinite loop during MSM interpretation.
This has been fixed.
-Added more ereader .properties settings profiles
Settings profiles now available for:
- pc (personal computer or laptop)
- eeepad (Asus Eee Pad Transformer and Transformer Prime)
- touchpad (HP TouchPad)
- xoom2 (Motorola Xoom 2)
Contact me if you would like a settings profile added for your device.
-Better default settings for iPad 1 and 2
Disabled pdf output since cbz is better to read and faster to produce.
Download the latest version from the MangAI project page.
Some Manga Scan Model logic improvements coming soon.
Did a lot more logic work than I thought I would. Even Manga Publication Model logic, which has been solid for some time now, got new tweaks to better handle some rare cases.
Lots of testing to do. Expect a release in the next few days.
The new logic is looking good. If the final round of testing goes well, then I should be able to release v1.03 tomorrow.
During final testing I found some areas that could use improving. v1.03 release has been postponed.
-Update-
Kinda figured out what was going wrong in one of my test cases. It has do with sorting scans of the same publication where the volume and chapter specification levels vary. So some scans can have just volume info, some just chapter info, some both volume and chapter, some neither volume or chapter, and then you also have to worry about the special types of pages (front cover, insert, special, back cover, credit). You may think that you just sort first by volume, then chapter, then page, but the reality is you have to look at the whole picture. For example, v#_c?_p# should appear before v?_c#_p#?. You have to account for special page type as well, so v#_c?_p#? special, back cover, or credit should appear after v?_c#_p#?.
I was already covering most the above cases but had forgotten to consider v#_c? vs v?_c#. Testing the new code now.
I’m glad I delayed v1.03 since I’ve been able to implement some great logic tweaks and improvements. Still working hard and expect a release in the next few days.
Latest tests look good. v1.03 should be out tomorrow.