Re: [platform-dev] Changing default IAdapterManager in Platform?

I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=576024 as we are facing yet another issue because of this limitation (in supporting multiple adapters from editor to IToggleBreakpointsTarget this time). ___ platform-dev mailing list platform-dev@

Re: [platform-dev] Changing default IAdapterManager in Platform?

On Fri, Nov 29, 2019 at 4:34 PM Jonah Graham wrote: > I think the case that Mickael brings up here (which originated from here > ) is a case where > the extra context is already being passed in. The adaptableType already has > the context th

Re: [platform-dev] Changing default IAdapterManager in Platform?

I think the case that Mickael brings up here (which originated from here ) is a case where the extra context is already being passed in. The adaptableType already has the context that is needed to properly resolve - however unlike the column i

Re: [platform-dev] Changing default IAdapterManager in Platform?

Hi Mickael, This is the common software evolution problem, now we want to consider multiple instances instead of the single one. We have very similar problem for JFace label/content providers. Let me illustrate it with ITableLabelProvider that extends its "contextless" parent with methods like

[platform-dev] Changing default IAdapterManager in Platform?

Hi all, We've got an interesting case with LSP4E vs LinuxTools, both registering a factory with the same signature (adptableType -> adapterType). The dummy expectation was that it was legal to have multiple factories and that as long as the current factory returns null, another one would be tried