have a results object in the view model to collect results; this could help when searching with multiple threads, as the results may come in out of order and having them in a collection, we could use LINQ to sort them
we could then bind the available and not available areas to the object, instead of writing out to a textbox manually
rough idea for class:
class SearchResult {
DateTime resultDate;
List availableTimes;
bool hasAvailableTimes; /optional since this data could be found by checking the length of availableTimes/
}
and in the main view model, add this prop that can be bound to the form:
IQueryable SearchResults;
have a results object in the view model to collect results; this could help when searching with multiple threads, as the results may come in out of order and having them in a collection, we could use LINQ to sort them
we could then bind the available and not available areas to the object, instead of writing out to a textbox manually
rough idea for class: class SearchResult { DateTime resultDate; List availableTimes;
bool hasAvailableTimes; /optional since this data could be found by checking the length of availableTimes/
}
and in the main view model, add this prop that can be bound to the form: IQueryable SearchResults;