- ArchiveViewer: instead of using unzip and to support more formats
(only CBR & RAR for now)
- NewsDownloader & Wikipedia plugins: instead of using `ZipWriter`
- device: re-implement `Device:unpackArchive` and get rid of device
specific `untar` implementations
- readerui: instead of using unzip for document provider detection
Currently you can only toggle page turn buttons to inverted or not. This
commit adds the ability to also have an option in dispatcher to set the
value instead of just toggling.
This can be useful for profiles that want to set the value rather then
toggle.
ATM you can only toggle G sensor lock in dispatcher, this commit adds
the ability to set the lock to on or off.
This can be useful in profiles that want to set an explicit mode
instead of toggling the setting.
- Updated changelog with proper version & date.
- Updated description (based on common metadata)
- Removed duplicated files that are condensed in /usr/share/doc/koreader
Misc:
- make `frontend/device/devicelistener.lua` non executable
- make `plugins/terminal.koplugin/profile` executable
* GestureDetector:adjustGesCoordinate: Remove one layer of indirectiçon in
direction translation
That function call wrapper felt pretty unnecessary to me ;).
* GestureDetector: Translate complex gesture positions, too
i.e., if there's a start and end position, translate those, too.
Fix#13090
Problem: when you install Kiwix from FDroid or as a standalone apk (ergo not via
the Play Store) it installs as `org.kiwix.kiwixmobile.standalone`, which before
this commit isn't supported.
This commit simply just adds it as a seperate option :)
It's relatively easy to miss-click the buttons, especially on devices
with questionable touch panels...
And while doing so is perfectly fine, you miss the InfoMessage telling
you that the update will be applied on restart, which is potentially
confusing.
Re: #12674
The only codepath that sets pending_connection to true in NetworkManager calls turnOnWifi right after, so we can't really ever see pending_connection w/o isWifiOn being also true ;).
kobov4 exists solely because there's a dedicated TC for it,
but we don't distribute binaries for it (it doesn't differ enough from
kobo, and experience has taught us that this kind of split was not a
great idea (e.g., kindle5 vs. kindlepw2)).
kobov5 targets a massively updated userland, and requires further
changes, including to the delivery mechanism, so it very much warrants a
dedicated package (re: #12401)
Get rid of the weird interaction between device implementations,
`ffi.util` (`isSDL`, `noSDL`) and the device input code: each
device knows if it's using SDL or not, so rely on that to load
the right underlying input implementation.
Using `require` didn't make much sense since most of them are only used in a single place anyway, and it takes care of a few weird interactions in the process (besides not polluting `package.loaded` with useless crap ;)).
On Monza, the lift frame can report these for *multiple contacts* without an id or a slot, which is super-duper invalid -_-".
(And we have ABS_MT_POSITION_X & ABS_MT_POSITION_Y for the "saner" frames, plus these devices generally don't support pens, so we don't make use of pressure).
(Also, switched to a dedicated handler like for the phoenix quirks, to avoid bogging down the standard handler with hacks for broken drivers).
Fix#11910
I don't even remember how badly things broke (at least on old devices) without it, despite it making absolutely no sense at all (state-extended just flips a global that dictates whether some things get flagged as wakeup sources or not).
So, don't rock the boat too much: we don't remove it, but instead of using a sleep, we use a task deadline instead, which ensures we'll keep processing input events in the right order in the meantime. We'll already have neutered input by this point, so we'll only process power events anyway.
That means that the only iffy things are potentially *when* and *where* we have to potentially cancel that task. Resume makes sense, of course, and we log an info message to make the log flow clear; but we also do so in suspend... just in case. With a warning log because that probably indicates something fishy went on.
Also cleanup the comments while I'm there, and actually rewrite the wakeup_count stuff properly so it could actually theoretically be used if ntx kernels were actually reliable. Spoiler alert: they're not, this is still horribly broken on at least Mk < 7. Works just fine on a Forma, though, so, yay.
Fix#12325
