These are chat archives for WildGums/Orc.Controls

10th
May 2017
Frank Monroe
@fmonroe
May 10 13:13
I downloaded this and ran the Example code; the FilterBox in the sample code does not work. It throws "System.Windows.Data Error: 40 : BindingExpression path error: 'PropertyName' property not found on 'object' ''FilterBoxViewModel' (HashCode=2018156051)'. BindingExpression:Path=PropertyName; DataItem='FilterBoxViewModel' (HashCode=2018156051); target element is 'AutoCompletion' (HashCode=46586415); target property is 'PropertyName' (type 'String')". Help please.
Geert van Horrik
@GeertvanHorrik
May 10 13:27
Is it the example? They are probably useless binding errors (the binding will work)
Frank Monroe
@fmonroe
May 10 13:31
No the app/example does not behave as shown on the web page: when I type 'd' it does not show a list of entries with 'd' as shown on the FirlterBox screen shots at https://github.com/WildGums/Orc.Controls.
Geert van Horrik
@GeertvanHorrik
May 10 13:32
Thanks, we will look into this.
Geert van Horrik
@GeertvanHorrik
May 10 13:51
Build - 1.6.0-unstable.47 should be up in about 5-10 minutes, could you please try that one?
Frank Monroe
@fmonroe
May 10 13:52
yeas - thanks.
Geert van Horrik
@GeertvanHorrik
May 10 13:52
If you find any other issues, feel free to report them, we are happy to fix them :)
Frank Monroe
@fmonroe
May 10 13:53
That's very reassuring. I don't want to be a trouble. I like Catel and the associated frameworks for LOB apps.
Geert van Horrik
@GeertvanHorrik
May 10 13:53
If you report an issue, it's a potential issue for us, so we like to fix those. So you are never a trouble.
Frank Monroe
@fmonroe
May 10 14:51
OK. This is much better. But I think this is an issue: <orc:FilterBoxControl ... PropertyName="Value" FilterSource="{Binding ListOfPersons}" Text="{Binding FilterText}" /> the name of the property for the FilterSource seems to be hard-coded to FilterSource. The code ignores my ListOfPersons list and binds instead to a FilterSource list (this may be a newbie issue).
Frank Monroe
@fmonroe
May 10 15:22
Opened Issue #23.
Frank Monroe
@fmonroe
May 10 20:47
#23 is fixed and tested.
Geert van Horrik
@GeertvanHorrik
May 10 20:47
Nice, thanks for letting us know.