Complex binding paths conventions

Sep 15, 2010 at 10:54 AM

Hi Rob,

thanks for a great job! In Change set 470e7c544d06 you added support for Complex binding paths. It would be nice if it will be possible to turn "underscore convetion" off globally or/and to specify "convention character".



Sep 15, 2010 at 1:46 PM

What character would you use besides underscore?

Sep 15, 2010 at 6:31 PM

Thanks for your reply. I would use any non-frequent character - for example X, Q or W in my native language (czech). I use Caliburn Micro in application, where names of bounded fields needs to mirror name of fields in existing database. Many fields in existing database contains underscore due to ten-years-existing conventions. So I can not use underscore as "convention character", but I can use another one (Q character is never used in any name of field  - if I am not wrong, non of czech-origin word contain Q character). Resume: I do not want to give up using complex binding path convention but I can not use underscore character. Maybe "double underscore" string convention will solve my problem, but I can imagine someone else can use "double underscore" as existing another-purpose convention. Thanks and sorry for my pure English.

Sep 15, 2010 at 7:33 PM

I recommend replacing the ViewModelBinder.BindProperties method with your own implementation, substituting the character you prefer.