Why doesn't gallery module use menu_set_location()? Also, gallery's breadcrumb is wrong.

I don't understand why the gallery module goes through so much work to set the page title and breadcrumb when all it needs to do is call menu_set_location(). I upgraded to a more recent release of the Gallery Module thinking that it would actually integrate with the menu system only to find that it only adds its OWN menu, it still doesn't integrate correctly (well, at least I don't think it operates the way I would expect...)

The gallery modules seem to think that a callback function and menu item is required to register within Drupal's menu system, but I don't think that is true. If Gallery would only take all of the work that it does to figure out the tree to (incorrectly) set the breadcrumb, and instead use menu_set_location, it would get the correct page title, the correct breadcrumb(and actually, I think it's currently doing this incorrectly too, see below), and way more: any menus that the user had set up to correspond to an album or item name would automatically become active, and any blocks that depended upon a certain link becoming active would show automatically. I'm pretty darn sure that this automatic behavior, this true menu integration, is what the menu_set_location function is for, and yet the gallery module doesn't use it. Why not?

I'm about to embark on programming in this functionality for myself, I've needed it on several projects and it's a must for my current project. Before I do this, if someone can tell me why it's not already in the gallery module, or even if you can tell me who I might ask about this, I'd really appreciate it. I just think that the menu integration in the gallery module appears fundamentally flawed.

OH, and the call to the set_breadcrumb seems incorrect, too. It doesn't work the same way for nested albums as for top-level ones, and it leaves off the outermost leaf (which is wrong since drupal pops it off before display).