NanoClock: Yet another persistent clock - Page 14

NiLuJe · 04-23-2022, 07:43 PM

Oops, that's because the fix was actually incomplete -_-".

Released v0.11.3, then

.

Deobulakenyo · 04-24-2022, 02:47 AM

Quote:

Originally Posted by NiLuJe

Oops, that's because the fix was actually incomplete -_-".

Released v0.11.3, then

.

i confirm the "disappearing nanoclock after Calibre eject ' is solved.

Thank you, NiLuJe.

I hope you won't abandon nanoclock. This is easily the top addon to the kobo reading experience for me.

NiLuJe · 04-24-2022, 06:49 PM

It's pretty much feature-complete, so it's not like it requires much of my time anyway

.

jbs · 06-04-2022, 06:58 PM

Quote:

Originally Posted by NiLuJe

It's pretty much feature-complete, so it's not like it requires much of my time anyway

.

I've had my Kobo Libra H2O for a year or so now and really love it. The one thing I was occasionally missing was a persistent clock. Today I decided to look into it a bit further, found this thread, installed it and LOVE it. Thanks so much!

Once I got it installed I spent a little while trying out different fonts and thought if it doesn't already exist that this might save others some time. I tested a dozen or so fonts while appending the NAME of the font to my string, then took pictures. The last 4 - UNSCII, ALT, THIN and IBM all look identical to me so I'm guessing that means they don't exist on my device. But I really like Spleen so that's what I'm using.

Thank you SO much NiLuJe - you've made my beloved reader even a bit more beloved to me!

NiLuJe · 06-04-2022, 07:12 PM

Unscii is very similar to the old IBM BIOS font, but not exactly (e.g., the zero's crossbar).

As for its variants, the constants are actually unscii_alt, unscii_thin, unscii_fantasy, unscii_mcr & unscii_tall (hadn't noticed before that the documentation is wrong for those [it's pointing to the constant names used by the FBInk CLI instead of the API]).

(c.f., http://viznut.fi/unscii/ for more about unscii)

----

EDIT: Released 0.11.4 to fix that in the config comments.

Deobulakenyo · 06-04-2022, 09:32 PM

Quote:

Originally Posted by jbs

I've had my Kobo Libra H2O for a year or so now and really love it. The one thing I was occasionally missing was a persistent clock. Today I decided to look into it a bit further, found this thread, installed it and LOVE it. Thanks so much!

Once I got it installed I spent a little while trying out different fonts and thought if it doesn't already exist that this might save others some time. I tested a dozen or so fonts while appending the NAME of the font to my string, then took pictures. The last 4 - UNSCII, ALT, THIN and IBM all look identical to me so I'm guessing that means they don't exist on my device. But I really like Spleen so that's what I'm using.

Thank you SO much NiLuJe - you've made my beloved reader even a bit more beloved to me!

How did you put the font name as aprt of the displayed clock?

jbs · 06-04-2022, 11:01 PM

Thanks for the explanation and the update! I'll update my screenshots with some more of the fonts. I think I can speed up the process a bit by pre-making the ini files and then just dropping them in one by one.

I've noticed that my current format string overlaps the chapter information in the middle of the screen. I think the answer is no but is there any option for having a left justified portion and a right justified portion? For example:

format_left=L:{frontlight} B:{battery}
format_right=%I:%M

The only way I've figured out how to get the information to those spots is to insert the right number of spaces in the string, but the spaces themselves overlap the chapter information.

I'm SO loving having a clock again, thanks!!!

Quote:

Originally Posted by NiLuJe

Unscii is very similar to the old IBM BIOS font, but not exactly (e.g., the zero's crossbar).

As for its variants, the constants are actually unscii_alt, unscii_thin, unscii_fantasy, unscii_mcr & unscii_tall (hadn't noticed before that the documentation is wrong for those [it's pointing to the constant names used by the FBInk CLI instead of the API]).

(c.f., http://viznut.fi/unscii/ for more about unscii)

----

EDIT: Released 0.11.4 to fix that in the config comments.

NiLuJe · 06-05-2022, 01:55 PM

Quote:

Originally Posted by jbs

The only way I've figured out how to get the information to those spots is to insert the right number of spaces in the string, but the spaces themselves overlap the chapter information.

Yeah, that's the sanest approach

(It's not build for fancy formatting).

Depending on your pen color setting, you might be able to avoid stomping on the UI bits behind your spaces by enabling the backgroundless mode

.
(That won't work on the Sage & Elipsa, though).

Ned · 06-23-2022, 05:11 PM

I wonder if someone who understands Macs could tell me how to install this please using my iMac?
I used 'The Unarchiver' app to unpack the zip with the Kobo root on my Libra 2 as the destination, but it did not overwrite the .kobo file, merely created another hidden file alongside it called .kobo1.

JSWolf · 06-23-2022, 05:12 PM

Quote:

Originally Posted by Ned

I wonder if someone who understands Macs could tell me how to install this please using my iMac?
I used 'The Unarchiver' app to unpack the zip with the Kobo root on my Libra 2 as the destination, but it did not overwrite the .kobo file, merely created another hidden file alongside it called .kobo1.

Don't install NanoClock on your Libra 2. It can cause your Libra 2 to be unstable.

Ned · 06-24-2022, 03:01 AM

Quote:

Originally Posted by JSWolf

Don't install NanoClock on your Libra 2. It can cause your Libra 2 to be unstable.

Ah, thank you Jon. You've saved me a lot of pain.
I'll go for Miniclock then

JSWolf · 06-24-2022, 04:09 AM

Quote:

Originally Posted by Ned

Ah, thank you Jon. You've saved me a lot of pain.
I'll go for Miniclock then

Before installing Miniclock, I suggest you find out if it works with the latest firmware on a Libra 2.

frostschutz · 06-24-2022, 04:54 AM

miniclock is unmaintained and won't work with latest firmwares - at the very least, the patch to no longer grab input events exclusively so miniclock can listen in, no longer works for current firmware so you would have to patch it manually, and you'd also have to update fbink manually for device support...

I doubt that miniclock could fix any issue that nanoclock has... its an issue with the device itself, anyhow

NiLuJe · 06-24-2022, 06:37 AM

Yup, the issue is in how the driver (fails) to deal with the refresh pattern we trigger, the exact variant of *Clock used is barely relevant

.

Ned · 06-24-2022, 07:11 AM

Oh no!!
So I'll have to do without the onscreen clock and battery!
What a blow.

But thank you guys for setting me straight before I tried it

ps Is there any hope of a clock being developed that works despite the failings of the device/drivers?
Or shall I resign myself to its absence?

06-04-2022, 07:12 PM	#200
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Unscii is very similar to the old IBM BIOS font, but not exactly (e.g., the zero's crossbar). As for its variants, the constants are actually unscii_alt, unscii_thin, unscii_fantasy, unscii_mcr & unscii_tall (hadn't noticed before that the documentation is wrong for those [it's pointing to the constant names used by the FBInk CLI instead of the API]). (c.f., http://viznut.fi/unscii/ for more about unscii) ---- EDIT: Released 0.11.4 to fix that in the config comments. Last edited by NiLuJe; 06-04-2022 at 07:24 PM.

06-24-2022, 04:54 AM	#208
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	miniclock is unmaintained and won't work with latest firmwares - at the very least, the patch to no longer grab input events exclusively so miniclock can listen in, no longer works for current firmware so you would have to patch it manually, and you'd also have to update fbink manually for device support... I doubt that miniclock could fix any issue that nanoclock has... its an issue with the device itself, anyhow Last edited by frostschutz; 06-24-2022 at 05:14 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Cover images not persistent	gogu1904	Kobo Reader	5	08-21-2020 11:55 AM
PW2 jailbreak not persistent	chrnit	Kindle Developer's Corner	3	01-06-2017 09:16 PM
Persistent Display?	jessie102	Sony Reader	2	03-08-2010 10:45 PM
Persistent WIFI connection.	tovarish	iRex	2	11-16-2009 04:30 AM

04-23-2022, 07:43 PM	#196
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Oops, that's because the fix was actually incomplete -_-". Released v0.11.3, then .

04-24-2022, 06:49 PM	#198
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	It's pretty much feature-complete, so it's not like it requires much of my time anyway .

06-23-2022, 05:11 PM	#204
Ned Ebook reader Posts: 389 Karma: 5899335 Join Date: Oct 2008 Location: York, England Device: Kobo Aura H2O (ed 2, v1), Kobo Forma, Kobo Libra 2	I wonder if someone who understands Macs could tell me how to install this please using my iMac? I used 'The Unarchiver' app to unpack the zip with the Kobo root on my Libra 2 as the destination, but it did not overwrite the .kobo file, merely created another hidden file alongside it called .kobo1.

06-24-2022, 06:37 AM	#209
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Yup, the issue is in how the driver (fails) to deal with the refresh pattern we trigger, the exact variant of *Clock used is barely relevant .

06-24-2022, 07:11 AM	#210
Ned Ebook reader Posts: 389 Karma: 5899335 Join Date: Oct 2008 Location: York, England Device: Kobo Aura H2O (ed 2, v1), Kobo Forma, Kobo Libra 2	Oh no!! So I'll have to do without the onscreen clock and battery! What a blow. But thank you guys for setting me straight before I tried it ps Is there any hope of a clock being developed that works despite the failings of the device/drivers? Or shall I resign myself to its absence?