[BEHAVIOR PATCH-4910 only] UserSettings

[chinajade]

Attached you will find a 'patch' version of the UserSettings behavior valid for HB-2.0.0.4910 only. This behavior will automatically be included in post-4910 releases.

Update: HB-2.0.0.4910 was slipstreamed to include this fix. If you do a fresh download, you don't need what's posted here.

The patched behavior addresses the following problems:

USERSETTINGS- Changed in the following ways:

• Addressed the removal of the UseExperimentalStuckHandler setting from the HBcore
• [wiki]Honorbuddy Custom Behavior: UserSettings[/wiki] Wiki page updated to reflect latest set of 'valid' settings

So why does UserSettings 'keep breaking'?
UserSettings has not been modified in a very long time. It was designed to automatically adapt to most changes made within the HBcore.

However, in the last couple of drops, the HBcore has changed in ways that UserSettings cannot automatically adapt. UserSettings was designed to throw exceptions when this situation occurs, so the problem could quickly be located, and repaired. In our opinion, this beats the pants off of silently failing, or worse, corrupting things.

The last couple of releases of HBcore introduced changes that were not communicated. Its life, this is precisely why software development cycles have "Test" releases. But at least we know where the problem lies and how to rapidly repair it.

We apologize for any inconvenience this has caused the Community.


cheers & enjoy,
chinajade

 

[nokdu]

Cheers Mate

 

[Kickazz006]

woot

Also - i've added a Dev Behaviors QO (alliance - sw) for quick tests w/ a few runto's to annoy the stuck handler in my svn (useful stuff folder - starts in SW). this is useful for when we need to test behaviors - especially the most common ones such as FlyTo, UserSettings, UserDialog and possibly disabling the stuck handler temporarily (from the profile writers end)

 

[vlad0327]

These things happen because HB devs don't give users enough information on the upcoming or already implemented changes. Considering that HB is not a standalone program and has support for various modules there should be a separate thread or some other kind of communication base for more advanced users such as profile/plugin/CC writers.
Change list given in the release thread is simply not enough for development purposes.