HintProxyFabric does not support custom HintProxies for already registered Controls
Is your feature request related to a problem? Please describe. I am building a MultiSelectComboBox on top of the default WPF ComboBox, so that i can use as much of the default styles and features provided by this toolkit. See this sample project. And while i got that already working, i'd like to adjust the SmartHints provided by this toolkit to work with my solution aswell.
The problem i am encountering is, that HintProxyFabric will only consider the first registered builder for a given type and ignore any others that might be more apropriate, but have been added after the default ones.
Describe the solution you'd like I'd like to insert my own builder at any position i like in the builders collection...
Describe alternatives you've considered or adjust the lookup logic to something that takes inheritance into account aswell. The first approach is probably easier and preferable, but i am open to any solution.
Additional context
I want to provide my own IHintProxy in HintProxyFabric for a derived ComboBox, but the current setup will ignore my registration, because therealready is a default IHintProxy for ComboBox registered.
Sample project can be found here: https://github.com/Insire/MDIX_ClearButtonCommand
I'd be happy to provide a PR to get this going.
@Insire I sure hope you found a solution to your issue, since it's been so long since you reported this! If you still have suggestions that could turn into a PR, that would be very welcomed as well.
I totally forgot about this issue. I'm pretty sure i wrote my own control back then following MVVM and moving as much logic as possible into the viewmodel, so that i could reuse code and still benefit from MDIXT.
That being said, my description seems to be pretty on point on what i expected to happen and i probably pick could this back up.
If you have a suggestion on which approach to take or any alternative, i could look into this again.
@Insire I believe the HintProxyFabric and IHintProxy for certain things (focus detection in particular - see here) has been down-prioritized in MDIX in favor of SmartHint.HintHost.
This might be a good opportunity to bring the SmartHint.HintHost up to feature-parity with the IHintProxy and prioritize the prior in all cases; not just focusability. That could be worth looking into...
This issue is marked stale because it has been open 30 days with no activity. Remove stale label or update the issue, otherwise it will be closed in 14 days.
This issue was closed because it has been stalled for 14 days with no activity.