BeHierarchic 4.1 menu bugs: a follow-up

Regarding yesterday's reports of problems with BeHierarchic 4.1: many users wrote to confirm the report.

Clarifications Carlos Rodríguez wrote: "I have all the problems described regarding BeHierarchic 4.1. However, I would like to offer some clarifications:

The problem with the incorrect display of the Apple menu content and that also affects the menu bar clock seems to be an extension conflict because it is not present with Apple's basic set and only BeHierarchic enabled - of course Apple Menu Options off.

Regarding the click on the About command of the front application, what happens is that the click is passed to what is behind this command. If the front application has a window in this position nothing happens, but if there is no window of the front application at that location the click is passed to what is behind."

FAXstf conflict work-around Joshua Rafofsky received the following reply from the author of BeHierarchic regarding the FAXstf conflict: "There is a work-around: Let BeHierarchic loads first (before FAXstf extensions). For example, you can put BeHierarchic in the Extensions folder. If you want a convenient access to BeHierarchic, you can then alias the one in the Extensions Folder and put this alias in the Control Panels folder." Alternatively, if you have Conflict Catcher, you can use it to modify the load order.