On 02/28/2014 05:30 PM, Paul Webster
wrote:
Except how is your migration manager able to "see"
the old definitions? You must still have the commands defined,
right? As long as that is true, your best bet is to change
their names to "Whatever (deprecated)" and migrate the
keybindings. Then in your next release don't provide the old
commands.
Yes, I have the old + new commands hardcoded into the migration
manager. Renaming them is not nice but should at least solve
confusion when users look to the key binding page.
re: deleting commands. Commands aren't deleted, but they can be
undefined. After you've removed the Bindings for the commands
you want to get rid of, you could try
org.eclipse.core.commands.Command.undefine() (I'm not 100% sure
of what it'll do though).
I'll try out the undefine() method and report back how it works.
But ... they are defined by the runtime system after reading the
extension points. They can be added back if something causes
the system to re-read the extensions.
PW
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
