Quote:
Originally Posted by tshering
Thank you for this information. However, I am not quite sure how to use this information. The content of the koreader.sh is the same as it was in koreader_kobo.sh, isn't it.
Looks great to me. I could make some good use of it. Another thing I would welcome is, if input.lua could check the Kobo Touch model, if this is the decisive information, and handle the reversal of the x/y coordinates.
I cannot see how this effects whether koreader is or is not reopening the last read book, if settings.reader.lua got lost? Or did you refer to some other point?
|
I noticed pazos's "changes" at github and while it makes sense for the project to go in that direction, having a separate script to call reader.lua in the Start Menu is very handy. No matter what name you give it. Yes, the content and function is the same, the "kobo" distinction is being removed because the code for the different device families is being consolidated into their own folders.
pazos:
The way you have posted this, both here and at Github, makes me wonder if you were unaware that reader.lua already has the arguments that you talking about? In fact one of the benefits of having a koreader launching script in kbmenu is that the arguments that I have applied to reader.lua remain in place, when updating koreader. I have provided reader.lua with the path to my library on the external uSD, as it's first argument for a long time now.
Having the "Start in last open file" as an option in koreader's menu is much more convenient, than doing it by changing the reader.lua argument (although that works, as well), Having my Start Menu koreader_kobo.sh with my reader.lua argument as I want it has had no apparent effect on the koreader option, works fine.
As to the mini crashing, I would look to some impact from the recent "Mini Only" firmware update.
Luck;
Ken