Cat Menu Settings Aren't Applied After They Are Changed On Container

it seems like there is a lot of discussion/issues related to category menus. while i have read the threads/issues here i'm not sure anyone has completely answered or asked exactly about my issue.

i believe it is a bug that could be fixed. But I ALSO BELEIVE THERE IS A WORKAROUND FOR IT IN THE IDE (E.G. DRUPAL inteface via admin settings etc) AND I ACTUALLY AM MORE INTERESTED IN SOMEONE SHARING THAT WORKAROUND KNOWLEDGE HERE SO THAT OTHERS CAN BENEFIT FROM IT IN ONE PLACE VERSUS BEING BURRIED IN THE SUPPORT FORUM POSTS.

Here's a simple scenario:

1) create menu in admin/menus -> call it 'menublock'
2) go to admin/blocks and enable 'menublock' so it appears on the left sidebar
3) set default menu in admin/settings/category to the 'menublock'
4) create a container called "SECTIONS":

apply the following settingst:

- doesn't matter if it's hidden or not
- applied to type 'page'
- required (for page types)

under category menu settings:

Enable 'Menu items within this container:'
Enable Menu items for assigned nodes:

Submit the container

5) add a category to "SECTIONS" called 'history'

6) create a page called 'test' and assign it to SECTIONS-> history

OK, category menu works just fine because IT IS THE FIRST TIME YOU CREATE THE CONTAINER. What you should see is the menublock in the left sidebar with the applied cat menu settings and it will look like this:

menublock
- SECTIONS (Container - assuming not hidden)
--history (category)
--- test (assigned node)

Perfect! That's what we want.

Here's the problem though. The minute you go in and change ANY CAT MENU SETTINGS ON THE ORIGINAL ROOT CONTAINER (SECTIONS IN THIS CASE), and submit the changes, the menu does NOT reflect the changes (at least it doesn't on my system)?? What? This seems to contradict what is explicitly said by the module developer here http://category.greenash.net.au/multiple_root_menus.

For instance, lets make a real obvious cat menu setting CHANGE on CONTAINER SECTIONS:

First we leave our target default menu to 'menublock' in admin/settings/category

Then under category menu settings for CONTAINER SECTIONS:

DISable 'Menu items within this container:'
DISable 'Menu items for assigned nodes':

Then save/submit the settings for teh container.

What menublock SHOULD LOOK LIKE IS THE FOLLOWING:

menublock
- SECTIONS (Container - assuming not hidden)

NOTICE: there are no menu items for either categories (history) or assigned node (test). HOWEVER, THE MENU STILL LOOKS EXACTLY THE SAME AS IT DID BEFORE YOU SUBMITTED THE CHANGES! You can make these changes back and forth ad infinitum on the container SECTIONS and no matter how many times you submit the changes, the menu still looks exactly the same.

OK, i don't care that it's a bug or even if it's the way it's supposed to function. WHAT I DO CARE ABOUT IS HOW I CAN MAKE CHANGES TO A CONTAINER'S CAT MENU SETTINGS TAKE EFFECT ON THE TARGET MENU!!!
Because at some point in the future when i least expect it, i'm going to have to make one of these changes. And if i have 200 nodes and categories structured under my SECTIONS CONTAINER, and i decide i don't want to display assigned nodes, i'm going to have to know how to make that reflected in my menus. And i have no idea how to do that right now.

So how does one do this?

Ironically, as i said above, according to the documentation here:

http://category.greenash.net.au/multiple_root_menus

changes on a 'root' element should always override admin/menus. Which means my container cat menu settings changes should always override the menu items and be reflected accordingly. Unless i'm misunderstanding something here.

Sorry for the long post but i believe clarity is often missing from these posts/issues so i tried to spell out the problem as best i could.

Any and all replies to this are very welcome