taxonomy_term view does not work with "Group categories" block

Trying to revive this thread.
I tried everything possible to get the taxonomy_term view - which emulates the standard Drupal display for terms, offering the possibility to customize the display - working with the OG Vocab Group categories block. The OG group context is lost as soon as one hits a term.
I tried the default argument with group context, php code..., filter, etc... no way.

If someone has succeeded at this, I would be very glad to benefit the experience.
Thanks

There don't seem a huge interest for this... quite strange!

I really tried everything, there was no way to keep the context from the Group Category block using a view with a path.
Because it was really critical for me to master the taxonomy browsing display in OG, I finally decided to swim a little bit in PHP coding and found a rather simple) solution. I am really not skilfull enough in PHP, Drupal and CVS to submit a patch, so I just tried to show the diffs with +/-

In og_vocab.module:

function og_vocab_block_view() {
  $group_node = og_get_group_context();
... 
-    $tree = array_slice($tree, 0, 20); // removes a puzzling 20 terms limitation
...
// change to pass group argument
-    $items = og_vocab_build_list_items($index = 0, $tree);
+    $items = og_vocab_build_list_items($index = 0, $tree, $group_node->nid); 
...

// change to handle group argument
- function og_vocab_build_list_items(&$index, $tree) {
+ function og_vocab_build_list_items(&$index, $tree, $gid) { 
...
// add group argument in the path to term views
-     $term_path = "taxonomy/term/$term->tid";
+     $term_path = "og/term/$term->tid/$gid";
...
// add group argument in each item
-      $items[] = array('data' => $item, 'children' => og_vocab_build_list_items($index, $tree));
+      $items[] = array('data' => $item, 'children' => og_vocab_build_list_items($index, $tree, $gid));

This basically
1) gets rid of the 20 items limitation making this block unusable (this limitation and the absence of complaints might indicate that nobody uses the Group category block) - I have vocabs with 200+ terms, it works perfectly.
2) add the OG context to the item path so the url passed to the view will be og/term/tid/gid

Then a clone of the taxonomy_term View is modified as follow:
path: "og/term/%"

Arguments:
Taxonomy: Term ID (with depth)
Organic groups: Groups / Node ID from url

With this modification, OG Vocab no longer works with the core Drupal taxonomy display which responds to the original path "taxonomy/term/%"
This is because OG context has to be passed as an argument, which conflicts with the variable "depth modifier" argument that needs to get out.
It might be possible to overcome this problem by a smarter handling of arguments, but my Drupal and Views knowledge stops here.
If it is not possible, then OG Vocab would have to come with a View as described above (and so will have a dependence to Views)

Hint1: Look at what Taxonomy menu has done, offering the choice of the default core handling and custom view, to be set in config by the user so each vocab can have a specific view
Hint2: OG Vocab block could be a submodule of Taxonomy-menu as both modules share a lot in common.
Taxonomy menu as the advantage to be menu based, so DHTML works

If the maintainer or someone else interested and competent enough could approve the change and submit a patch, this would be a path toward a great usability improvement of OG Vocab.

Now, I am perfectly happy with OG and OG Vocab!!!

Keeping on top of my list
This is a deadly needed feature!
adding to this request
http://drupal.org/node/877558
I had to move away from this block and implement it another way:
- defining one block per vocabulary using Taxonomy Menu
- Condition its visibility using

<?php
$node = og_get_group_context();
if ($node->nid == XX) {
  return TRUE;
  }
else {
  return FALSE;
  }
?>

where XX is the group nod ID where this vocabulary bock will be allowed to appear

Though this allow great looking browsing and Views display, this far from ideal because it needs a manual setting each time a group is added.

Actually, I was returning to it.
The other problem I complain is
http://drupal.org/node/877558

But the manual workaround in #5 was unbearable as soon as group creation is under users' control.

greta_drupal, have you modified your view as indicated in my post?