Bruce,
The problem with the update is that the package name internal to the .wepm file for version 3.2 is cuckoo_clock_32, while the internal package name for the .wepm file for version 3.3 is just cuckoo_clock, so WE and appGet is seeing it as two different packages. And, this is indeed what happened to me: when I installed version 3.3 it did not uninstall version 3.2, leaving me with two copies running. This is going to be a hard one to fix. Chip From: BX [mailto:[email protected]] Sent: Monday, April 29, 2013 9:19 PM To: [email protected] Cc: GW Aaron Smith Subject: Re: cuckoo clock laptop problem still happening Hi Chip, I tried replying to this email and it was sent back, saying it was too long. So I had to delete all other stuff before this email. I had noticed that last night when updating my Windows 7 computer that the cuckoo clock was not listed for update. I also checked and discovered the flag for notifying others is in fact checked at the web site end. Don't know why, but apparently that check box is not working, at least for the cuckoo Clock app. I guess I will have to write to Aaron and see what is going on. Sincerely Bruce Sent: Monday, April 29, 2013 6:48 PM Subject: RE: cuckoo clock laptop problem still happening Thanks Bruce. You may want to ask GW for some help with your update, for whatever reason, but Window-Eyes through the add/remove apps dialog, and when using apGet, neither of these show your latest upload as an update to the cuckoo clock program. I don't have any ideas as to what is causing this, but to try to see it for yourself, reinstall your 3.2 version and then use WE or appGet to see if there are updates. This means though, assuming it's happening to everyone, that people won't be made aware that you've updated the program. Thanks. Chip
