ApplicationCommandManager un-registering


#1

 

Hey Jules -

I recently started including my global AppCommandManager in a SharedResources object.

When scanning plugins, some of my plugins use SharedResource pointers, and some also add themselves as commandTargets.

Unfortunetaly, since the lifetime of the commandManager in shared space is now longer than the plugins .... I get some issues.

 

So ... long story short ... could you maybe add a method to UN-register for commands from the AppCommandManager? That would solve a bunch of issues here.

 

Thanks as always

A


#2

You mean like ApplicationCommandManager::removeCommand​ ?

Hope this helps!

 

 


#3

 

 

Not quite.

I don't want to remove the command, I want to remove one of the LISTENERS to the command.

 


#4

 

 

Not quite.

I don't want to remove the command, I want to remove one of the ApplicationCommandTargets that the manager knows about.

 

 

Actually, it looks like the manager doesn't maintain a list ... just the first target, which then leapfrogs to new ones.

So ... I think setFirstCommandTarget is basically what I need.

 

Cheers!

A