NickelClock: Show time while reading

[Deobulakenyo]

I do not know what I am doing wrong but any whole number i put does not change the clock location in the X axis. I started with 1, 10, 65, 450. nothing. the clock is still at the same default location.

[xyclonei]

Originally Posted by Deobulakenyo

I do not know what I am doing wrong but any whole number i put does not change the clock location in the X axis. I started with 1, 10, 65, 450. nothing. the clock is still at the same default location.

Are you using the artifact build or the initial one?

Try using the attached latest artifact build to see if it works.

[Deobulakenyo]

Originally Posted by xyclonei

Are you using the artifact build or the initial one?

Try using the attached latest artifact build to see if it works.

That was the problem. I did not how to use that "artifact".

For the sake of instruction, how was one use that using the original koboroot as in the original zip file?

[sherman]

Sorry @Deobulakenyo, I should have just attached the test build here. I'll do that in the future.

Thank you @xyclonei for attaching it.

[xyclonei]

This artifact build is a newer version incorporating adjustable margins.

The installation is the same. Drop the KoboRoot.tgz file within the zip into the .kobo folder and it should auto-update.

[Deobulakenyo]

Thank you, sherman and xyclonei.

The problem is my ignorance. Thanks for all the help


BUT can you explain to me what and how the latest changes should be used? on my end, what I understand is that the github release page is still the original (initial one) nickelclock.

Are the changes supposed to be integrated (don't know if this is the proper term) to a new installer?

I do not understand what the build. artifact build means. Looking at the release pages, it is still v. 0.1.0 and was uploaded 13 hours ago.

BTW your (xyclonei) upload a few posts back work fine.

[sherman]

Originally Posted by Deobulakenyo

Thank you, sherman and xyclonei.

The problem is my ignorance. Thanks for all the help


BUT can you explain to me what and how the latest changes should be used? on my end, what I understand is that the github release page is still the original (initial one) nickelclock.

Are the changes supposed to be integrated (don't know if this is the proper term) to a new installer?

I do not understand what the build. artifact build means. Looking at the release pages, it is still v. 0.1.0 and was uploaded 13 hours ago.

BTW your (xyclonei) upload a few posts back work fine.

So, every time I push a change, a new KoboRoot.tgz is generated automatically, and these can be downloaded as an artifact (inside a NickelClock.zip file). These are used to test changes, and provided as a convenience so others do not have to compile the changes themselves. Artifacts are not intended for the general user. Consider them test builds.

When I am happy with the changes, I will make a new release, with an updated version (next will be 0.2.0), which will be available on the releases page.

Apologies for the confusion this caused.

[Deobulakenyo]

Originally Posted by sherman

So, every time I push a change, a new KoboRoot.tgz is generated automatically, and these can be downloaded as an artifact (inside a NickelClock.zip file). These are used to test changes, and provided as a convenience so others do not have to compile the changes themselves. Artifacts are not intended for the general user. Consider them test builds.

When I am happy with the changes, I will make a new release, with an updated version (next will be 0.2.0), which will be available on the releases page.

Apologies for the confusion this caused.

I get it now. I learbed a few new things today. Thanks

[Ned]

Originally Posted by sherman

Introducing NickelClock, a mod that shows the kobo time widget while reading.

On the other hand, NickelClock should not have any stability issues on new devices, especially the Libra 2, So, if you're a Libra 2 owner missing your clock, might I suggest this one?

Thank you - there's nothing wrong with one more clock, especially when having just got a Libra 2 I find that Miniclock and the other new one will not work so I am clockless.

I had indeed lost all hope when the other wizards had said all hope is lost, so may I say you have made my day

[Ned]

And in minutes, your mod is added to my Libra 2 and Forma, moved to the Top Left where I want it. And so much nicer and cleaner than the Miniclock I was using on the Forma. Thank you again.

Edit: No tweaks needed, I'm just glad to have a clock visible

[sdothum]

i am not sure whether this is doable but the horizontal margins appears to be scaled (larger) when one rotates to landscape mode. If this orientation is detectable by the widget, adding an optional second comma separated parameter to hor_margin (or separate var for landscape mode) would offer the last bit of tweaking for the anal

Regardless, this is a great widget!

[sherman]

Originally Posted by sdothum

i am not sure whether this is doable but the horizontal margins appears to be scaled (larger) when one rotates to landscape mode. If this orientation is detectable by the widget, adding an optional second comma separated parameter to hor_margin (or separate var for landscape mode) would offer the last bit of tweaking for the anal

Regardless, this is a great widget!

I cannot reproduce this on my Glo, or Forma. The margin appears to be the same no matter the orientation. Can anyone else reproduce?

[sdothum]

Originally Posted by sherman

I cannot reproduce this on my Glo, or Forma. The margin appears to be the same no matter the orientation. Can anyone else reproduce?

i apply kobopatch with custom left/right margins.. i wonder if this is only discernible if the selected margin (its percentage value) is large enough?

To clarify: the hor_margin setting fixes the time in a precise location in portrait or landscape mode. But the landscape margins for the text is the same percentage as for portrait orientation, hence, a wider width (unless one reads with no measurable side margins i.e. margin width is zero percent).

[sherman]

Originally Posted by sdothum

i apply kobopatch with custom left/right margins.. i wonder if this is only discernible if the selected margin (its percentage value) is large enough?

Probably. I don't use that patch, so I don't know how it behaves.

I don't think I will try and mitigate this, it will add complexity to NickelClock for little benefit to most users. I'm trying to keep NickelClock as simple as I can.

[sdothum]

Originally Posted by sherman

I don't think I will try and mitigate this, it will add complexity to NickelClock for little benefit to most users. I'm trying to keep NickelClock as simple as I can.

i don't believe kobopatch alters the handling of margin settings -- kobopatch just allows defining custom percentages (versus the default 1 percent increments).

But i agree with you. It is not a huge issue visually -- as a user of both orientations, i just need to set a "middle" value offset.