MobileRead Forums - View Single Post

frostschutz · 11-07-2018, 04:39 AM

@LucyOne:

I think you have to set retainStateOverRestart to yes

otherwise it will always say invertActive = no and miniclock looks for invertActive = yes

@Ripplinger:

could it be the same issue?

otherwise the only thing I can think of... miniclock checks the timestamp of the file, and only looks at the file again if the timestamp changes. and that timestamp does not have microsecond resolution, but is actually a 1-second or even 2-second window.

So if you somehow manage to turn it on and off again in quick succession, miniclock might be stuck on the wrong value. I'll have to do some more testing if this is actually a case.

11-07-2018, 04:39 AM	#104
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	@LucyOne: I think you have to set retainStateOverRestart to yes otherwise it will always say invertActive = no and miniclock looks for invertActive = yes @Ripplinger: could it be the same issue? otherwise the only thing I can think of... miniclock checks the timestamp of the file, and only looks at the file again if the timestamp changes. and that timestamp does not have microsecond resolution, but is actually a 1-second or even 2-second window. So if you somehow manage to turn it on and off again in quick succession, miniclock might be stuck on the wrong value. I'll have to do some more testing if this is actually a case.