-
Notifications
You must be signed in to change notification settings - Fork 8
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
Create control for generating a FieldPath #7
Comments
Conceivably this could also be represented as a Benefits are that everything is visible which makes comprehension faster. Downsides is that it requires screen real estate up front whereas the stacked combo idea only requires as much space as their are fields chosen. Also, recursive fields like the example below would make the tree problematic unless it was loaded on demand (which is OK).
|
As per the comments in #7, a TreeView is a faster method of adding lots of fields so this has been added. Whole subjects can be added by dragging the subject (or relation field) nodes. Can't reorder or delete output fields yet. Will still need a combo box version as it's needed in the advanced search.
Mostly comments on how it will operate in the adapter. No real code as of yet.
Adapter completed with appropriate tests to back the functionality. Now to create the UI part.
Current implementation clears and recreates all combos on every change (and then some). It should at least loop over the combos and check references to data source and only recreate the combos if the references change. This might help the issue where the combo SelectedItem doesn't stick too. |
Fixed in d37a15b |
Take existing logic from
dbqf.WinForms.Advanced.AdvancedPartView
and create a control that stacks combos (and adds/removes them) as the user chooses fields that have relationships to other fields.Allow the control to take a
FieldPathFactory
so at any depth of the path the next set of fields can be retrieved.This control can be used for the user-defined output field selection and for the advanced search control. Later this control can be developed in WPF and whatever else.
The text was updated successfully, but these errors were encountered: