clock.lua (alpha DL on beta 3 push)

[Anonymous]

Howdy! just some blind firing testing to see what would happen.

I miss cosmos a LOT, so I decided to let the patcher update itself a couple times, then launch WoW. It actually is almost working!

There was one message I hit OKAY too:

Interface\FrameXML\Moneyframs.lua]:70 attempt to call global 'unitmoney' (a nil value)

and then it got stuck on a Clock.Lua message:

"Interface\FrameXML\Clock.lua"]:175 attempt to perform arithmetic on field 'timesincelastupdate' (a nil value)

This is not a complaint, I know I use this at my own risk.

Hope this can help with some debugging on the beta3 push!

[Anonymous]

i get that error too =)

[Anonymous]

I am also getting this error, I also try to go into cosmos via game control to try shutting options off and can click anything, even okay/cancel have to hit esc to get out.

[Anonymous]

I have also found that the Cosmos Option menu is no longer available in the current build of Alpha. It also, by default, puts all the extra bars up and cannot (obviously) be removed since the Cosmos Option menu is no longer there...

Tsrah

[Anonymous]

For some reason the patcher isn't updateing everything needed for Cosmos to run. Try going to Configure -> Complete File Check

[AlexanderYoshi]

Howdy! just some blind firing testing to see what would happen.

I miss cosmos a LOT, so I decided to let the patcher update itself a couple times, then launch WoW. It actually is almost working!

There was one message I hit OKAY too:

Interface\FrameXML\Moneyframs.lua]:70 attempt to call global 'unitmoney' (a nil value)

and then it got stuck on a Clock.Lua message:

"Interface\FrameXML\Clock.lua"]:175 attempt to perform arithmetic on field 'timesincelastupdate' (a nil value)

This is not a complaint, I know I use this at my own risk.

Hope this can help with some debugging on the beta3 push!

Alright, these should be fixed now.

[geowar]

The Military Time checkbox doesn't seem to be working (the clock always displays a 24 hour clock). Looking at the code it appears that

function ClockFormat(value, checked)
MilitaryTime = checked;
end

should be

function ClockFormat(toggle)
MilitaryTime = toggle;
end

At least this fixed it for me.

It also appears that the time zone slider doesn't initialize to the previous (saved?) value (although the clock appears correctly). This may just be a limitation of the implementation of the cosmos slider control. Seems like the "on load" event code should be able to set the sliders initial value from the saved setting so that it appears correctly when the cosmos prefereces dialog appears. -- [\minor quibble] ;-)

[geowar]

Ok, my bad; none of the clock prefs (time zone, military, etc.) are remembered.

Oh boy! I get to learn something else! ;-)

[geowar]

The prefs problem is global; nothing to do with the clock bug; The lastest alpha fixed the military time bug but now the slider is wack. Want's to go from 0.0 => 1.0. Nothing wrong with he clock code; it's a bug in Cosmos slider control. Wierd since the health/mana shout slider work correctly.