Jump to content

MediaWiki talk:Gadget-UTCLiveClock.js

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Alex Smotrov (talk | contribs) at 19:11, 17 September 2008 (One tick per minute: comments: separate page, some duplicate code). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Font size

I've just installed this into my account after using the original version by User:Mathwiz2020. Enlarging the font of the clock makes the rest of the personal toolbar look out of place (like its touching the page tool tabs). Is it okay if I change the font size back to match the rest? --wL<speak·check> 12:44, 15 January 2008 (UTC)[reply]

I designed it based on the reality of mine to have the personal toolbar at the left, so personally I would like to have it larger. AzaToth 17:17, 16 January 2008 (UTC)[reply]
Mines twitches like a dying animal: is this a problem with my browser (Mac, Firefox, no add-ons)? I can't for the life of me figure out what's up with it. Anthøny 11:25, 20 January 2008 (UTC)[reply]
Strike that; I still had VoA's clock gadget installed (importScript('User:Voice_of_All/UTCclock.js');), so the two were essentially clashing. Fixed :) Anthøny 11:28, 20 January 2008 (UTC)[reply]

Browser access-key conflict

I'm not sure if this is the correct page, but it's the closest I could find. I run IE6 and IE7 (on different partitions, but same comp) on WinXP/SP2. When the "UTC LIVE clock" feature is activated throught eh Gadgets in Preferences, the "Undo" function in the Windows right-click and Ctrl-U functions is disabled. I'm a lousy typist, so this is a function I need to have, but I like the UTC time feature also. After several weeks without my Undo, I finally tried disableing each new feature in Gadgets, and discovered that the CLock was the apparent culprit (my undo works now, anyway!) Is there a fix or work-around to this problem? Thanks. - BillCJ (talk) 09:11, 15 February 2008 (UTC)[reply]

This might not suit you, but I usually press Ctrl + Z to undo, which you might find easier. Mahahahaneapneap (talk) 01:33, 24 February 2008 (UTC)[reply]
I just tried that, and it does not work either. Evidently it's the "undo" functionalitly, not just the right-click undo feature. - BillCJ (talk) 01:57, 24 February 2008 (UTC)[reply]
I can confirm that this is indeed a problem in IE because of setTimeout(), but I'm not sure how to fix this at the moment. —AlexSm 04:07, 24 February 2008 (UTC)[reply]

One tick per minute

I have a rather old and slow computer, and I use Firefox. So I can not use this gadget since it slows down my browser way too much. How about changing it so it only ticks once per minute? I don't see why people would need the seconds? And having the seconds tick must be distracting, right?

Or if you want to keep the seconds, make a second gadget with minutes only.

--David Göthberg (talk) 21:35, 22 April 2008 (UTC)[reply]

Some time ago User:Saintrain brought up the same issue in a discussion at the Village Pump. I have now gotten around to update my version of the clock with the improvements suggested by Ilmari Karonen and others in that discussion. It is now fully configurable to meet all needs. Due to it being fully configurable it is now more code, but it is more efficient than any of the other versions since it is only the very small inner "updateTime" function that runs on each tick.
I have not installed my version of the clock as the gadget yet, since I think some users should test it first. But it works in all three of my browsers, even in my very old Internet Explorer 5.5.
If you would like to test it you can copy my version of the clock from User:Davidgothberg/monobook.js and put it into your own monobook.js.
Note: There are several code snippets on my monobook.js page, be sure to copy the right part. Oh, and don't forget to configure the DavidClock to tick and show as you like. As you can see I have it set to only tick once every 5 minutes since I have a very slow computer and don't really need higher time resolution.
--David Göthberg (talk) 16:56, 17 September 2008 (UTC)[reply]
It would be a bit more convenient if you made it a separate page, and then we could test the script simply by pasting javascript:davidClock=30;importScript('User:Davidgothberg/clock.js');void 0 into the browser address field. As for the code, the line else if( window.davidClock == 0 ) doesn't have any purpose, some code pieces could be combined together. And I suspect some current users will not be happy with the second "static" clock by default. —AlexSm 19:11, 17 September 2008 (UTC)[reply]

Inexplicable Bug?

I'll be pleasantly surprised if someone is watching this page, but I didn't want to bother WP:VPT for a non-critical puzzler. (Plus, this way I get to bump up my MediaWiki talk edits!) If I don't hear from anyone in a while, I'll try there.

OK, here’s the puzzle. I have the little clock/purge gadget installed. So far, it has appeared without incident on every page on Wikipedia except WP:ANI. Now, if I go into edit mode at WP:ANI, it’s there; but if I’m just viewing the page, it isn’t. The clock isn’t being covered up by anything; the rest of my personal toolbar just shifts over as if I didn’t have the clock installed. Purging pages, logging out and in, etc. doesn’t work. I have no idea if it’s always been like this, or if it’s a new phenomenon, but I’d love to know why this is happening. --barneca (talk) 19:06, 24 July 2008 (UTC)[reply]

What browser are you using? It works for me in the Mac version of Safari and Firefox. -- Ned Scott 07:41, 5 August 2008 (UTC)[reply]
Hmmm. It works for me now too. In a way, that's a shame, because now I'll never know what was going on, and it's irritating not to know. But, to answer your question, when it wasn't working, I'm 100% sure it wasn't working in IE7, and if my sometimes unreliable memory serves, I'm 90% sure it also wasn't working in Safari (not sure what version, I'm not near that machine right now). --barneca (talk) 12:26, 5 August 2008 (UTC)[reply]