Group Calendar 4 

Your observations hit the nail on the head -- if it's really fixed, bumping is best. If it isn't really fixed then /deepsigh

I wish I had more time, because then I could get a guild who's having this problem a lot to try getting everyone upgraded and see if it goes away. I guess everyone in the guild alliance that helps me test on my server is good about having their clocks set correctly because this issue seems to very rarely come up.

You can make personal events such as Doctor, Dentist, Vacation and 'Other' which will not be shared. Your tradeskill cooldown events are also not shared.

Your events will be visible from any of your alts, including those on other realms and factions and you will get reminders while on alts.

v4.3b3 Changes

- BUGFIX: Fixed whisper UI to correctly ignore Blizzard holiday events
- BUGFIX: Event databases not owned by a player will no longer be pruned for expired events
- BUGFIX: "Changes won't appear until synch is done" dialog won't appear during normal player database pruning at startup

I think I've found the problem causing the "events changed from another computer" bug. In order to keep your cached databases small, Group Calendar automatically goes through at startup and removes events older than two weeks (or whatever your /cal history command sets it to if different). If someone in the guild has their computer's clock set to a whacked date in the future, then when they log on they'll go through and start purging everyone's events from their calendar and then proceed to send out those changes to the network.

They should get the "your clock is wrong" dialog, which several people have been reporting getting, but really it's too late by then and besides, most people seem to think that message is Group Calendar's problem and not their own.

I'll make two changes to fix this:

1) Group Calendar 4.3b2 uses the new server date functions that patch 3.0 added so it won't matter so much what your clock is set to

2) I'll modify the database code so that you never purge events from cached databases no matter how old they are. They'll get purged when the owner logs in and his calendar purges them and then sends an update out instead.

Assuming this is the culprit, the only way to fix it would be to get everyone to update (yeah, painful, I know).

So here's my question to you guys since your the main users: should I bump the protocol number so that GC4.3 will not talk to older versions, thereby avoid the problem from ever happening, or should I leave it compatible with all other 4.x versions and you rely on getting everyone to update their GC and/or make sure their computer date and time zone settings are correct?

I've been avoiding posting them there to save myself some time. I will absolutely be posting the release builds of Outfitter and GC there, but I want fast turnaround on downloads and bug reports to get everything ironed out before Thursday.

What I really need to do is take some time to develop an automated process for posting builds to wobbleworks.com so that I can use that as my primary portal for betas and primarily post release builds here and on Curse.

The WoW server downtime today isn't helping any of my efforts much though. I've got a build of both addons with bug fixes (including some code to help me track down the persistent "updated from another computer" problem), but I can't test them at all today.

The bug wasn't what I thought it was -- it's caused by my hack to get the Blizzard events into GC's display. I use a fake user name of "_BLIZZARD" for built-in WoW events and there's no corresponding database for that 'user'. The whisper system wasn't modified to be aware of that possibility, I'll have it fixed for the next build.

I think there's a chance that those people could cause GC to complain about clock settings, but other than that I can't think of any potential problems. I should take out the time check completely so that people won't even risk getting the "adjust your clock" dialog any more.

You're right that I forgot to document the modified-right-click opening the time manager -- I'll have to get that in the release feature list at least. I was going to put it in the tooltip, but it's starting to look really cluttered with the other click instructions. Maybe I'll move those tips to the 'newbie' tooltip that shows up in the bottom right corner of the screen instead of putting them in the main tooltip itself.

Whoops, that looks like a bug. As I learn more about how to program in Lua I've been gradually converting Group Calendar and Outfitter to be more object-oriented (I'm a C++ programmer primarily), but it looks like when I changed the whisper stuff into an object I missed some references. I'll take a look and get that cleaned up.