function widgetOnLoad()
{
eval(datetimecore1.get("%WeekEn")).Font.Color = rgba(41,1,214,255);
}

{
eval(datetimecore1.get("%AMPM")).Font.Color = rgba(197,16,16,255);
}

function datetimecore1OnUpdate(Sender)
{
eval(datetimecore1.get("%WeekEn")).Font.Color = rgba(41,1,214,255);
eval(datetimecore1.get("%AMPM")).Font.Color = rgba(197,16,16,255);
eval("num"+datetimecore1.get("%Hour0")).Font.Color = rgba(0,93,171,255); //hour0
eval("min"+datetimecore1.get("%Minute0")).Font.Color = rgba(0,20,171,255); //minute0
}

//To reduce system resources this code only need to run if the time/seconds = 0
//this could be add with an IF statement at the start of the function datetimecore1OnUpdate(Sender)

Also the make it work properly on start up you need the function widgetOnLoad() to be added to WIDGET - FUNCTIONS - ONLOAD - ( currently it is not running at startup. )

function widgetOnLoad()
{

}

Without it the widget will start work on the next minute right...?

What I have to add it in the space..? (I have to copy the entire code?)

Please read my last edited post to correct a mistake I made.

No the code is OK as you have it, it is not being called to run at startup
to get it to run the function widgetOnLoad() at startup
Click DESIGN button in the toolbar to go to design mode
Click on WIDGET in the top left side column
Click FUNCTIONS under widget attributes, the blue box on top of the right side column
In the OnLoad edit box SELECT scripting code
it should take you to the function widgetOnLoad() you have already created.

now it will run at startup.

Tomorrow I will put the seconds adding the corrisponding lines in the script..

Not sure what you mean, but remember the update code only runs every minute at 0 seconds.

function datetimecore1OnUpdate(Sender)
{
if (eval(datetimecore1.get("%Second")) == 0)
{
ResetAllColors();
eval(datetimecore1.get("%WeekEn")).Font.Color = rgba(138,0,178,255);
eval(datetimecore1.get("%AMPM")).Font.Color = rgba(197,16,16,255);
eval("num"+datetimecore1.get("%Hour0")).Font.Color = rgba(0,93,171,255); //hour0
eval("min"+datetimecore1.get("%Minute0")).Font.Color = rgba(0,20,171,255); //minute0
eval("sec"+datetimecore1.get("%Second0")).Font.Color = rgba(84,230,0,255); //second0
}
}

function ResetAllColors() // reset colors
{
for (var m=0; m<60; m++) // count up the minutes 0-59
{
eval("min" + ("0" + m).slice(-2)).Font.Color = rgba(0,0,0,0); // reset all mins to transparent
}
for (var h=1; h<13; h++) // count up the hours 1-12
{
eval("num" + ("0" + h).slice(-2)).Font.Color = rgba(0,0,0,0); // reset all nums to transparent
}
for (var s=0; s<60; s++) // count up the seconds 0-59
{
eval("sec" + ("0" + s).slice(-2)).Font.Color = rgba(0,0,0,0); // reset all secs to transparent
}
eval(AM).Font.Color = rgba(0,0,0,0);
eval(PM).Font.Color = rgba(0,0,0,0);
eval(Monday).Font.Color = rgba(0,0,0,0);
eval(Tuesday).Font.Color = rgba(0,0,0,0);
eval(Wednesday).Font.Color = rgba(0,0,0,0);
eval(Thursday).Font.Color = rgba(0,0,0,0);
eval(Friday).Font.Color = rgba(0,0,0,0);
eval(Saturday).Font.Color = rgba(0,0,0,0);
eval(Sunday).Font.Color = rgba(0,0,0,0);
}

//To reduce system resources this code only need to run if the time/seconds = 0
//this could be add with an IF statement at the start of the function datetimecore1OnUpdate(Sender)


function widgetOnLoad()
{
eval(datetimecore1.get("%WeekEn")).Font.Color = rgba(138,0,178,255);
eval(datetimecore1.get("%AMPM")).Font.Color = rgba(197,16,16,255);
eval("num"+datetimecore1.get("%Hour0")).Font.Color = rgba(0,93,171,255); //hour0
eval("min"+datetimecore1.get("%Minute0")).Font.Color = rgba(0,20,171,255); //minute0
eval("sec"+datetimecore1.get("%Second0")).Font.Color = rgba(84,230,0,255); //second0
}

if (eval(datetimecore1.get("%Second")) == 0)

this widget looks great!
if you can upload the widget,i think i can reduce the code and components.

i deleted all the "min" components
the second issue does not happen on my PC

I see that you used the empty background image that I made it at at the beginning!
About the num 42 I found it! You just used n41 twice!
The sec issue why happpens to me..?

Edit: I notice that the sec number that remains "on" is the sec AT THE MOMENT WHEN THE WIDGET LOADS.

I notice that the sec number that remains "on" is the sec AT THE MOMENT WHEN THE WIDGET LOADS.

{
ResetAllColors();
eval(datetimecore1.get("%WeekEn")).Font.Color = rgba(138,0,178,255);
eval(datetimecore1.get("%AMPM")).Font.Color = rgba(197,16,16,255);
eval("num"+datetimecore1.get("%Hour0")).Font.Color = rgba(0,93,171,255); //hour0
eval("min"+datetimecore1.get("%Minute0")).Font.Color = rgba(0,20,171,255); //minute0
eval("sec"+datetimecore1.get("%Second0")).Font.Color = rgba(84,230,0,255); //second0
}

//store reference to last, reset display on change
var lastmin = null;
var lastweek = null;
var lasthalf = null;
var lasthour = null;

function datetimecore1OnUpdate(Sender)
{
thisweek = datetimecore1.get("%WeekEn");
thismin = datetimecore1.get("%Minute0");
thishalf = datetimecore1.get("%AMPM");
thishour = datetimecore1.get("%Hour0");

//act if changed
if(lastmin != thismin)
{
if(lastmin != null) {
eval("min"+lastmin).Effect.Glow.Enabled = false;
eval("min"+lastmin).Font.Color = rgba(0,0,0,255);
}
eval("min"+thismin).Font.Color = rgba(0,20,171,255);
eval("min"+thismin).Effect.Glow.Enabled = true; //minute0
}

if(lasthalf != thishalf) {
if(lasthalf != null) {
eval(lasthalf).Effect.Glow.Enabled = false;
eval(lasthalf).Font.Color = rgba(0,0,0,255);
}
eval(thishalf).Effect.Glow.Enabled = true;
eval(thishalf).Font.Color = rgba(197,16,16,255);
}

if(lasthour != thishour) {
if(lasthalf != null) {
eval("h"+lasthour).Effect.Glow.Enabled = false;
eval("h"+lasthour).Font.Color = rgba(0,0,0,255);
}
eval("h"+thishour).Effect.Glow.Enabled = true;
eval("h"+thishour).Font.Color = rgba(0,93,171,255);
}
if(lastweek != thisweek) {
if(lastweek != null) {
eval(lastweek).Effect.Glow.Enabled = false;
eval(lastweek).Font.Color = rgba(0,0,0,255);
}
eval(thisweek).Effect.Glow.Enabled = true;
eval(thisweek).Font.Color = rgba(41,1,214,255);
}

lastmin = thismin;
lastweek = thisweek;
lasthalf = thishalf;
lasthour = thishour;
}

So this is what you asked! Isn't it? With blinking seconds???

Another version: Shows seconds in green, minutes in royal blue and avoids conflicts between seconds and minutes falling at the same time ex: 04:16:16 PM