Robert
d3e02d05c6
Fix: set custom screen DPI ( #5165 )
...
Settings -> Screen -> Screen DPI
When custom DPI is not set we see ugly information with %1:
2019-08-03 16:45:17 +02:00
Qingping Hou
fc69257660
fix: auto dpi menu checkbox display ( #4771 )
2019-03-11 10:01:37 +01:00
Qingping Hou
dd1ab7b409
bump base to decouple G_reader_settings from core
2019-03-03 13:10:45 +01:00
Frans de Jonge
8207e4bdf2
[fix, lang] More accurate auto-DPI text ( #4537 )
...
Simply don't mention any values when the device DPI isn't known.
A more robust auto-DPI info function could be added to Screen
but I'm not sure if it's worth the trouble.
Fixes https://github.com/koreader/koreader/pull/4389#issuecomment-454552446
2019-02-01 10:15:22 +01:00
Frans de Jonge
0407b577f5
[UX] DPI: show concrete numbers and add more custom DPI presets ( #4389 )
...
Follow-up of #4388 .
Implements the suggestion by @turkeyphant from <https://github.com/koreader/koreader/issues/2589#issuecomment-445474155 >.
Also adds a little explanatory message when holding on the Auto DPI option.
2018-12-08 21:12:18 +00:00
Frans de Jonge
e8192c8a04
[UX] Inform about hold to set custom DPI, up DPI limit to 900 ( #4388 )
...
* It was unclear that you needed to hold to set DPI, see https://github.com/koreader/koreader/issues/2589#issuecomment-445471384
* Up the DPI limit to 900 as several Android devices have already breached 800. This will increase the possibility of crashes due to a higher setting even on relatively high-DPI devices, but that was always already an issue.
* Also brings the custom DPI dialog box in line with the UX guidelines as per <http://koreader.rocks/doc/modules/ui.widget.confirmbox.html >.
2018-12-08 17:11:55 +00:00
Sergey Organov
48ff941764
Custom DPI: increase upper bound from 330 to 600
...
It's useful on 300dpi devices to get this value above 330 to enlarge
entire UI.
2016-12-01 18:03:33 +03:00
chrox
551857ce6e
fix some luacheck warnings
2016-06-28 00:43:23 +08:00
Hans-Werner Hilse
3066c86e38
Refactoring hardware abstraction
...
This is a major overhaul of the hardware abstraction layer.
A few notes:
General platform distinction happens in
frontend/device.lua
which will delegate everything else to
frontend/device/<platform_name>/device.lua
which should extend
frontend/device/generic/device.lua
Screen handling is implemented in
frontend/device/screen.lua
which includes the *functionality* to support device specifics.
Actually setting up the device specific functionality, however,
is done in the device specific setup code in the relevant
device.lua file.
The same goes for input handling.
2014-11-02 21:19:04 +01:00
