I had set it for .3 while experimenting with short periods and short refreshes, probably should be set higher (refresh lower) for general use, especially if you're going to stick with a one-conventional- second period on the clock. I had up to four of the running and hadn't noticed anything, but, yes, of course it's the clock refresh, the plugin is just called.
> It looked very .beatish :-) being a decimal in a Base > 60 code stream. Mmm... well, that's one of the arguments for Internet Time/beats. We already "go decimal" at both ends of the scale.. we count years in decades, centuries, millennia, there's no unit of 60 (or 24) years, or 60 of those.. and we also go decimal at the low end, with tenths of a second, hundredths, milliseconds, nanoseconds, and on down the scale, it's all decimal. Nobody in their right mind wanted to deal with units that were 1/60th of a second, and sub-units that were 1/60th of that, and so on. in the middle of the scale we have years, months, and days, that don't fit evenly and are awkward to deal with, but evolved because they corresponded to natural, real-world events, so there's some excuse and reason for dealing with a mess there. Nothing happens in the natural world 24 times in a solar day, though, or 60 times in one of those units, or 60 times in one of those, that's a purely "created" mess with no basis in reality, and it makes no sense to retain it in a new system for new uses (everyday, popular coordination of "global" events). Hence, the day divided into 1,000 "beats", same time everywhere. Keeps it clean, keeps it from being confused with the old system. On May 27, 9:37 pm, Morris Gray <msg...@symbex.net.au> wrote: > Thanks Tim, I saw that in the code and surmised that was the key to > what I wanted. It looked very .beatish :-) being a decimal in a Base > 60 code stream. I can now experiment on my own and decide what I want > to display how and when. > > Humour aside... I noticed my laptop fan running overtime. I traced it > to the NetTimePlugin > When a single example of the clock is running it consumes approx 30% > of processor time. Several running at the same time more than double > that. Both processors work really hard and the fan comes on almost > immediately > > To save trouble explaining and testing I have set up a Tiddlyspot test > site. > > http://tw-net-trial.tiddlyspot.com/index.html > > Is there a way around this? I really want this clock, there must be a > fix or another way. Maybe Eric can explain and help. > > Morris > > On May 27, 9:11 pm, rtimwest <rtimw...@gmail.com> wrote: > > > Morris, > > > Ok, it's done, and again (temporarily) running the clock in the title > > of my site, so you can easily check the behavior there to see if it's > > what you want without having to install it. > > >http://www.rtimwest.com > > > T. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
