Cosmos Patcher v3.5

[KarlKFI]

Here are some patcher updates for your 1.10 downloading pleasure. As usual there is more on the way.

Change Log Summary (v3.5):
* Added option to disable auto update of the patcher (until we can get it working correctly)
* Added option to surpress the change log
* Added an info button that shows information about the addon gleaned from the toc file.
* Added dependency checking for not installing and disabling AddOns in the install window.
* Added New Multi Selection check boxes to AddOn Manager
* Added Scan for nopatch files in AddOn Manager when installing AddOn
* Added required addons check when installing addons to alert to missing addons.

Visit the Full Change Log (http://www.wowwiki.com/Cosmos_Patcher_Change_Log) and our Download Page (http://www.cosmosui.org/index.php?p=download).

[Morac]

I clicked on "Restore Defaults" in the Cosmos2 options window and got an "unhandled exception" error.

I then checked a checkbox for unified protection, clicked "OK" and the program stopped responding.

Now any time I run it I get an "unhandled exception" error.

I deleted the "Cosmos Prefs" file and don't get the unhandled exception anymore, but I still can't press any buttons in the "Cosmos Setup" window. Well I can press them, they just don't do anything.

update: I managed to get it working by manually editing the "Cosmo Prefs" file and changing the "Run Setup" option to 0. Then I could get into the program and make changes manually.

I'm still getting a lot of beeping when moving my mouse over the Cosmos Patcher window with the configuration window open. This is probably because I have windows set up to focus on windows under the mouse since I get the same beep if I click on the window. It is annoying though.

[Morac]

I had to revert back to 2.2 because there are too many bugs in this version. Does 2.2 work with the new Thottbot addon since the location of the stored data is now in the SavedVariabled directory instead of the main SavedVariables.lua file?

If not can someone update 2.2 to upload the data until 3.X is bug free?

[easdem]

I cant get cosmos to work with the updated WOW... it says something like
"costumers with custum addons may have to uninstall...."
and no UI.... what dio I do??

[dormlock]

I clicked on "Restore Defaults" in the Cosmos2 options window and got an "unhandled exception" error.

I then checked a checkbox for unified protection, clicked "OK" and the program stopped responding.

Now any time I run it I get an "unhandled exception" error.

I deleted the "Cosmos Prefs" file and don't get the unhandled exception anymore, but I still can't press any buttons in the "Cosmos Setup" window. Well I can press them, they just don't do anything.

update: I managed to get it working by manually editing the "Cosmo Prefs" file and changing the "Run Setup" option to 0. Then I could get into the program and make changes manually.

I'm still getting a lot of beeping when moving my mouse over the Cosmos Patcher window with the configuration window open. This is probably because I have windows set up to focus on windows under the mouse since I get the same beep if I click on the window. It is annoying though.

That would probably be because the config window is a dialog and has to be closed before you can interact with the main window of the program.
If you have it set to focus on the window under the mouse then when it's trying to apply focus to the main window it can't because the config window is open. It's not a problem with the updater but with windows or whatever is doing the focusing for you trying to focus on a window you can't.

[dormlock]

I had to revert back to 2.2 because there are too many bugs in this version. Does 2.2 work with the new Thottbot addon since the location of the stored data is now in the SavedVariabled directory instead of the main SavedVariables.lua file?

If not can someone update 2.2 to upload the data until 3.X is bug free?

No it won't upload data and Thott probably won't update 2.2. A new version of the updater has already been submitted to so it'll be available soon for download. v3.7 fixes the setup problem and adds a exception logger that will help locate the problem with unhandled exceptions. Data uploading will not work in 3.7 as I wasn't aware until shortly that the data had moved to a new location. This change will easy to correct and there will be a new version tomorrow that will fix this and other issues. The new version would be today but i'll be working 11 hours today.

[Guar]

Any idea why the updater is hanging on its 1st run. It gets stuck at the Cosmos Setup screen. The one with the 3 pages. None of the cancel, next, or prev. buttons work. Any ideas?

[KarlKFI]

Cosmos Patcher v3.7 now availible for download.
Vist the change log: http://www.wowwiki.com/Cosmos_Patcher_Change_Log

[antifuse]

I'm having the same issues as Guar. Kinda sucky.

[babydaddy]

Rock on. Exception logging FTW!

[Grisu]

Now version 3.7 seems to be downloadable, but still got that "unhandled exception" error message when starting the updater. When turning "autoupdate at startup" of, than its fine, no error message. But the updater seem to work correct anyway when updating manually, but error messsage is not really nice for loved COSMOS... ;-)

Grisu :(

[Finwek]

I cant get cosmos to work with the updated WOW... it says something like
"costumers with custum addons may have to uninstall...."
and no UI.... what dio I do??

I had this same problem. Seems that during the new patch install Blizzard disables ALL Addons. So at your enter realm screen, click addons & re-enable those you need.

[Daeanor]

I cant get cosmos to work with the updated WOW... it says something like
"costumers with custum addons may have to uninstall...."
and no UI.... what dio I do??

I had this same problem. Seems that during the new patch install Blizzard disables ALL Addons. So at your enter realm screen, click addons & re-enable those you need.
That's not true at all. Anyone with any AddOns at all is getting the mnessage; it's generic and universal. I had ZERO of my AddOns disabled after updating. So, though I don't doubt you had yours disabled, don't say all are disabled for everyone. I had to disable a few (like two) after running because they were doing illegal operations, but other than that everything is working fine, and I still get that message when I log in.

[jgleigh]

Actually, I think what he meant was that each time they release a new patch they reset the Load Out of Data Addons switch. This has the tendency to disable most peoples addons.

[Finwek]

Actually, I think what he meant was that each time they release a new patch they reset the Load Out of Data Addons switch. This has the tendency to disable most peoples addons.

Thats what I meant. After enabling my various addons I also got the massive array of errors and had to disable a few addons. Just putting in my 2 cents worth since it sounded like the situation was simaliar.

[Geta-Ve]

Now version 3.7 seems to be downloadable, but still got that "unhandled exception" error message when starting the updater. When turning "autoupdate at startup" of, than its fine, no error message. But the updater seem to work correct anyway when updating manually, but error messsage is not really nice for loved COSMOS... ;-)

Grisu :(

Same exact problem, and it doesnt auto update :)

[dormlock]

I just sent 3.8 to karl and Gryphon it should hopefully be availale for download later in the day.

heres the changes
3.8
-- Fixed bug with auto patch
-- Fixed bug with auto run
-- FIxed Exception for IsCosmosAddon
-- Fixed multiple directories in the install window
-- Fixed cleaning bug
-- Updated the upload data to look for the new data locations in SavedVariables folder.
-- Added Addon colorizing of addons to red for addons that are missing a required addon.
-- Added Italic text to addon with notation for which folder is being defaulted to for Addons that exist in both AddOns and DisabledAdddons
-- Added dialog asking which to remove when the above occurs
-- Added Chain dependency disable dialog that will disable any addons that require an addon being disabled.
-- Added the ability to click the cell of protect and disable in addon manager to toggle value for addon.
-- Added button to run the test server enabled if WoWTest is in the wow folder.
-- Added option to use the test server when auto running.

[KarlKFI]

v3.8 live and avail on the download page.

[Morac]

Sigh,

It seems each release is worse than the last as most of the issues I'm hitting are things that worked in 3.0. 3.5 could at least check for updates. Oh well back to 2.0.2. It would be nice if I could upload Thottbot data, but at least 2.0 doesn't constantly crash.

My suggestion would be to move 3.X under alpha development and then update 2.0 to point to the new SavedVariables area. Then only after it has been thoroughly smoke tested, should 3.x be released. As it is now the Thottbot database is going to get out of date.


Issues with 3.8:

1. With the "Consolidated protection file" option off (unchecked). All addons are listed as protected in the Manage addon screen even if they are not protected. The button to unprotect non-cosmos addons still works as it removed the .nopatch files, but the GUI isn't updated to allow the user to reenable protection since they are always listed as protected. Manually checking the addons I wanted to protect and clicking "protect selection' did absolutely nothing (no .nopatch files were created). This was working in 3.5 so this is a regression.
If the "Unified protection file" option is on, then the correct protection state is displayed.

2. When I checked the option to "Use Consolidated nopatch file" in the cosmos2 configuration options and clicked okay, Cosmos starts using 99% of the CPU time and essentially hangs. I left it sits there for a few minutes before killing it. The only way to change this option is to edit the Cosmos Prefs file. This was also broken in 3.5, though it worked in 3.0.

3. Logging cannot be enabled. The logging preferences are not saved so the box is always unchecked when the advanced configuration page is opened.

4. Patching Cosmos results in an unhandled exception around 1/3 the way through the file check. On checking DamageMeters\Artwork\TitanDamageMeters.blp is where it hit the exception, most likely because this was a new file and didn't exist on my system. I confirmed this by using Cosmos 2.0 to patch and then running Cosmos 3.8 which made it all the way through the file checking process and then got an unhandle exception error trying to launch the installer.

5. The advanced options to hide the progress text and only update the progress after the nth file don't work. The progress text is still displayed and after every checked file. This is definately a regression since this worked in 3.0.

6. I can't be sure, but I don't think it's uploading the thottbot data. The reason I say so is that the data is still in the Thottbot.lua saved variables file after I run Cosmos*****.

7. Unhandled exceptions gallore. Pretty much every action results in an unhandled exception.

8. Then there's this:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 3/31/2006
Time: 5:57:18 PM
User: N/A
Description:
Faulting application cosmos*****, version 3.8.0.146, faulting module cosmos*****, version 3.8.0.146, fault address 0x00155745.

[Gryphon]

Sigh,

Sigh,

It seems each release is worse than the last as most of the issues I'm hitting are things that worked in 3.0. 3.5 could at least check for updates. Oh well back to 2.0.2. It would be nice if I could upload Thottbot data, but at least 2.0 doesn't constantly crash.

My suggestion would be to move 3.X under alpha development and then update 2.0 to point to the new SavedVariables area. Then only after it has been thoroughly smoke tested, should 3.x be released. As it is now the Thottbot database is going to get out of date.

I think you mean 2.20, which was the previous version written by Thott, of which 2.22 is currently available which does upload from Thottbot.lua, the link is on thottbot.com

3.5 was very broken, I don't see how you can say it was better than 3.8 at all. Your tone appears very condescending, we are quite lucky to have an updater application at all, we could just toss the app and offer zip files only if you prefer and you can manually update.

Realize that the author is doing this for free, he obviously doesn't run into these issues which is why feedback, constructive feedback, is neccissary.

Issues with 3.8:

1. With the "Consolidated protection file" option off (unchecked). All addons are listed as protected in the Manage addon screen even if they are not protected. The button to unprotect non-cosmos addons still works as it removed the .nopatch files, but the GUI isn't updated to allow the user to reenable protection since they are always listed as protected. Manually checking the addons I wanted to protect and clicking "protect selection' did absolutely nothing (no .nopatch files were created). This was working in 3.5 so this is a regression.
If the "Unified protection file" option is on, then the correct protection state is displayed.

2. When I checked the option to "Use Consolidated nopatch file" in the cosmos2 configuration options and clicked okay, Cosmos starts using 99% of the CPU time and essentially hangs. I left it sits there for a few minutes before killing it. The only way to change this option is to edit the Cosmos Prefs file. This was also broken in 3.5, though it worked in 3.0.

3. Logging cannot be enabled. The logging preferences are not saved so the box is always unchecked when the advanced configuration page is opened.

I too expierence these.

4. Patching Cosmos results in an unhandled exception around 1/3 the way through the file check. On checking DamageMeters\Artwork\TitanDamageMeters.blp is where it hit the exception, most likely because this was a new file and didn't exist on my system. I confirmed this by using Cosmos 2.0 to patch and then running Cosmos 3.8 which made it all the way through the file checking process and then got an unhandle exception error trying to launch the installer.

3.8 updated these files just fine for me, everything patches no problems at all. Patcher works as expected for me.

5. The advanced options to hide the progress text and only update the progress after the nth file don't work. The progress text is still displayed and after every checked file. This is definately a regression since this worked in 3.0.

A lot of changes were made to improve the application, these changes broke things, 3.8 isn't the end of all things.

6. I can't be sure, but I don't think it's uploading the thottbot data. The reason I say so is that the data is still in the Thottbot.lua saved variables file after I run Cosmos*****.

Agree, not sure if it is being uploaded.

7. Unhandled exceptions gallore. Pretty much every action results in an unhandled exception.

8. Then there's this:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 3/31/2006
Time: 5:57:18 PM
User: N/A
Description:
Faulting application cosmos*****, version 3.8.0.146, faulting module cosmos*****, version 3.8.0.146, fault address 0x00155745.

I expierece FAR less UE's than 3.5, nothing that hinders any normal operation.

Morac, it is great that you are providing feedback, but it would be nice if you just provided feedback without the negative remarks.

[babydaddy]

While I see improvement with each release and am gratelful, I do think that Morac has one good point: Treating what is currently the 3.x tree as a developmental alpha and simply maintaining the 2.x tree for changes to thott would eliminate some confusion. A feature freeze should also be considered at some point to allow bugs with current features to be worked out to a reasonable point prior to a release.

I'm sure, since I'm a feature/development junkie, that I'll continue to run Alphas whenever they mostly work. It's been really cool to see the feature set of the cosmos updater evolve into a sophisticated management tool as opposed to a sort of syncing tool.

A player friend of mine thought that cosmos was a for-profit shop, and just didn't know where the revenue came from. He was stunned to realize that it's just a bunch of players who just love WoW and want to develop cool tools for it. I think that says a lot when people take it for granted that your tools are part of a business plan rather than a simple hobby.

Many thanks to all team members. Your work makes the game more playable and more fun.

[Morac]

Morac, it is great that you are providing feedback, but it would be nice if you just provided feedback without the negative remarks.
I'm sorry if I was condescending, I'm just somewhat disenchanted with the new updater program. I subscribe to the KISS philosophy when it comes to GUI programs. I liked the 2.X Cosmos interface for it's simpllicity. It opened, uploaded, updated and launched Wow and it did so very quickly. I wasn't looking forward to being forced to replace it, so I lashed out some what (I didn't know about 2.22). I apologize for that. I realize other people like the new interface.

I do understand what it is to work on a program in your spare time for no money as I do so myself as well. I also know that people will complain when things don't work right. Sometimes I forget and do so myself. I do appreciate all the work that goes into Cosmos.

That said, like I mentioned previously, I don't agree with replacing 2.2 with 3.8 in it's current state. It would be nice if there was a link to 2.22 on the download page along side the link to 3.8 with 3.8 listed as in testing at least until 3.x is as nearly as stable as 2.22.

[Gryphon]

There is 100 'what you should do" ideas everyone has. It's a bit difficult to explain the system we currently have in place regarding 2.x vs 3.x, and even more difficult to type out. We are constantly working to make things easier for users, but we can only work so fast on it in our spare time. Only one person is coding the patcher, and doesn't have any other duties, so just like an addon, when it gets released you often find all the bugs you never saw and will need a bug fix.

Edit, Morac posted while I typed. I just want to mention nobody is forcing you to update, you can use 2.22 as long as you wish, I'm not sure if it will ever have 3.x pushed out through it, I'm sure that Thott will keep his own version updated. He just is not always readily available to the Cosmos team like the 3.x developer is, and 3.x is being developed to appease those who want more control over the application as well as being able to work as the 2.x version does for others.

[jgleigh]

The 3.x version also started as a patcher for Mac users. But I think the Windows users liked some of the new features so now it's cross-platform.

[KarlKFI]

Cosmos Re-released today: http://www.cosmosui.org/forums/viewtopic.php?t=14266

[Geta-Ve]

works for me :) Thanks guys! You are super quick

[BlackZam]

Why does the new patche suck so bad?
Im getting unhandled exception errors all the time.
And I can't get it to work for every second button I push gives me an error msg...

Please keep supporting the old 2.2 patchar...