Just a general reminder. Prior to making any releases, it is a good idea, always to run the wepm file locally. If you find it convenient, make another user profile under Window-Eyes, naming it things like: Instalation test. Then you can always make sure, your wepm file will work as intended, unless there would be user specific reasons. I have seen a few times, when packing did not go as expected, and the installation took another approach from what I intended. Letting a wepm out the door, without first having tested it to run, would be like letting the end-user do the beta-testing of your package. For most apps, trying to run the wepm file, should not take more than a couple of minutes. Yet, if you let out an untested wepm file, you create maybe half an hours work for yourself, and several complaining messages on the email server. Smile. So, do your testing, before letting anything out the door. The users will usually be ok, waiting five minutes longer, if they can be saved for a load of minor issues due to lacking testing from the developer.
Not saying that this would have solved anything in this particular case. Only making a general reminder to every developer. And, since you can perform this in a second user profile, it won't mess up any of your daily activity. You can even install other apps in this testing profile, that you don't normally use, but which might have given impact on your new release. And, you would easily be able to see, if the package will overwrite any files it should not, if it creates all subfolders as it should, and if it produces a user-friendly and smooth installation. The only thing you cannot really test, is in the event, that the app will be affected by any setting or other material, individually relating to the end-user's computer or usage. ----- Original Message ----- From: BX To: [email protected] Sent: Wednesday, May 01, 2013 1:39 AM Subject: Re: cuckoo clock laptop problem still happening Hi Chip, It is not too hard to fix, just have to go back to the one I renamed as 32 and put it back to the name, and go from there. I was wondering if that would happen because I get tired of the packing placing the web where I can not find it and decided to do this not thinking it would use the original name and not the new one. I think that should be address as a change for the packaging manager because after all when you save it, it asks for a name. In other words, if someone changes the name when saving, you have essentially created a nightmare just like we have. So, someone has to modify the packaging manager to reflect this save for it is actually not doing what you told it to do. Bruce Sent: Tuesday, April 30, 2013 6:42 PM Subject: RE: cuckoo clock laptop problem still happening 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
