I'm having a hard time understanding the decisions that lead to the current filter behavior. Essentially without doing a bunch of custom coding you get 2 options, neither of which are perfect.
You can either leave AutoPostBackOnFilter as false which requires the end user to either click a filter icon, or select a filter type. Or you get the set this true and get the auto postback which works for most examples well. I really beleive there should be a third option which removes the auto post back on defocus of the filter input. Here's why.
Set AutoPostBackOnFilter to true, and try to use the between filter on a date field. Here's how it went for me.
1. Enter two dates seperated by a space
2. Move mouse to select between fiter
3. Page posts back and throws a "String was not recognized as a valid DateTime" exception.
So, start again:
1. Select the between filter
2. Page posts back, sees the filter is blank and resets the filter value to blank again
3. Goto process 1
So, the only way to get these 2 to work together that I have discovered is to do this:
1. Enter 2 dates seperated by space
2. Unfocus
3. Let the page post back, throw an exception
4. Hit the back button
5. previous page displays, with filter data in field, unfocused
6. Select between filter
7. Page posts back and shows the correct data filtered
Please tell me I'm really missing something here. My end users are not going to want to see an exception like that. Nor do I want to trap the exception and hide it for when they do put crap into the text field.
Wouldn't it make some sense to have a few different options for how to deal with filters. For instance removing the onBlur postback behavior, or adding a search button. Seems to me both of these would require custom programming at this point. But I'd really like to see both become part of the core package.
In addition, it seems to me tht it would make a lot of sense to preserve the selection of the filter type, even if the filter field was blank. Then the end user could go about his business either way, by selecting a filter first, or entering data into the field first.
So for now, can somone give me some insight on how I might go about removing the onBlur auto post back behavior. I really like the hit enter to filter behavior and want to keep that.
Thank you in advance.
You can either leave AutoPostBackOnFilter as false which requires the end user to either click a filter icon, or select a filter type. Or you get the set this true and get the auto postback which works for most examples well. I really beleive there should be a third option which removes the auto post back on defocus of the filter input. Here's why.
Set AutoPostBackOnFilter to true, and try to use the between filter on a date field. Here's how it went for me.
1. Enter two dates seperated by a space
2. Move mouse to select between fiter
3. Page posts back and throws a "String was not recognized as a valid DateTime" exception.
So, start again:
1. Select the between filter
2. Page posts back, sees the filter is blank and resets the filter value to blank again
3. Goto process 1
So, the only way to get these 2 to work together that I have discovered is to do this:
1. Enter 2 dates seperated by space
2. Unfocus
3. Let the page post back, throw an exception
4. Hit the back button
5. previous page displays, with filter data in field, unfocused
6. Select between filter
7. Page posts back and shows the correct data filtered
Please tell me I'm really missing something here. My end users are not going to want to see an exception like that. Nor do I want to trap the exception and hide it for when they do put crap into the text field.
Wouldn't it make some sense to have a few different options for how to deal with filters. For instance removing the onBlur postback behavior, or adding a search button. Seems to me both of these would require custom programming at this point. But I'd really like to see both become part of the core package.
In addition, it seems to me tht it would make a lot of sense to preserve the selection of the filter type, even if the filter field was blank. Then the end user could go about his business either way, by selecting a filter first, or entering data into the field first.
So for now, can somone give me some insight on how I might go about removing the onBlur auto post back behavior. I really like the hit enter to filter behavior and want to keep that.
Thank you in advance.