-
-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search dropdown #3175
Search dropdown #3175
Conversation
d09169c
to
2b2dc4b
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2b2dc4b
to
640fc8c
Compare
Sorry for the inconvenience around builds with Mono 6. |
640fc8c
to
cc3d560
Compare
This comment has been minimized.
This comment has been minimized.
cc3d560
to
dd875d9
Compare
Found some :D
Apart from that, on the functional side it seems to already (or still :) work fine. |
dd875d9
to
3dfa772
Compare
Easy fix, force-pushed.
I can't find an event that fires when this happens. I've tried listening to all of the "close" and "lost focus" type events, but none of them seems to happen in these cases. Can you think of anything that might work?
I think this is because |
@DasSkelett, what do you think of the possibility of merging this and creating an Issue to track the glitches when the dropdown closes? I think a client with a top dropdown and odd alt-tab behavior would be preferable to the current one with a bottom expand-collapse. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. I've now used a ckan.exe compiled from this branch for some days, and everything appears to work fine, only exceptions the above mentioned points, which we can fix later.
GitHub confused by conflict resolution, merged in a7ad4af. |
Background / motivation
In #3041, we replaced the 3 old search fields at the top with 1 at the bottom, which can be expanded to to reveal 8 detail-level fields:
Initially during development I tried to keep the search field at the top, but I had trouble figuring out how to create a dropdown in WinForms that floats over the grid with editable controls in it, and it wasn't clear whether that was important. An expand/collapse (in the style of the above screenshots) on the top was jarring because it caused the top of the grid to jump up and down. Moving it to the bottom allowed those changes to be finished up and released with less risk of bugs, and I found examples of other applications that do just that:
We included this change in the v1.28.0-PRE1 pre-release and didn't hear a peep, but after it was fully released, multiple users expressed a preference for having the search at the top (see #3163).
Changes
Now the search is moved back to the top:
If you expand it, the other fields appear in a dropdown:
This is not easy to do in WinForms (there's not one simple switch to flip to turn it on; rather you have to tweak many poorly-documented settings in concert in just the right way), so careful testing is needed and quirks are likely to be found. In effect, the dropdown is a new top-level/standalone window with special flags set, with which the main window communicates from the outside.
Fixes #3163.