Need to Remove an Item from the GoTo menu

I would like to remove the Change Password item from the GoTo menu. I tried inheriting from LLLivelinkNavigationCallback into my module and modifying the Execute script so it would not create the Change Password item but the parent of my inherited module (LLLivelinkNavigationCallback) is still registered and is running also and it still creates the Change Password item. My new Execute script runs but the Change Password item has already been created. Am I missing something? Any help would be appreciated.

Find more posts tagged with

Comments

Marie_Lindsay_(MLindsay_(Delete)_15608)

I hesitate suggesting this without trying it first, but it sounds like you need to override an element of the fRegistry feature of the LLLivelinkCallbackNavigation object, rather than "enabling" a new LivelinkCallbackNavigation object and adding to the fRegistry feature. To override the subsystem object, I think you would:- add your NavCallback orphan to your OSpace's Globals, then- add a line like this to your Root object's Startup() method:$LivelinkNavigationCallbackSubsystem.fRegistry.LLLNavigationCallback = $YourOSpace.YourLLLNavCallbackObjectRefI have no idea whether this would work, but I'd love to know, so let me know if you try it.

Van_Duong_(tridentadmin_-_(deleted))

Because I am kind of new to this Builder environment, I may be doing something wrong and would appreciate the help. I my orphan "UserModsLLLivelinkNavigationCallback" to my Ospaces globals. My module is called USERMODS. I then added the following line to my Root object's Startup() method:$LivelinkNavigationCallbackSubsystem.fRegistry.LLLivelinkNavigationCallback = $USERMODS.UserModsLLLivelinkNavigationCallbackWhen I run it I get an error on that statement that says "An Object Value is not Specified".I would appreciate it if you could tell me if I am doing something wrong.Jeff

Marie_Lindsay_(MLindsay_(Delete)_15608)

I wonder which object value isn't specified? Is your statement at the end of your startup script? (It needs to be after the .Globals.Initialize() statement). Otherwise, I'm not sure what to suggest.