-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
DomainContextHandler does not handle feature "position" within the domain #6721
Comments
The above case is almost solved by specifying: v2 = ContextSetting(None, exclude_attributes=True) The only remaining problem is that However, because |
For remembering states of combo boxes where we choose features we tend to use contexts. We frequently use
DomainContext
, which works well most of the time.It works so well that I did not notice, until now, that it is not appropriate if combo boxes within the widget are limited to a different subset of (attributes, class_vars, metas).
Here is an example:
Running the test gives:
Is this a bug in DomainContextHandler? No, it is how it was designed; it is just that I was using it wrongly. For this kind of situations, I'll need a new type of context.
PerfectDomainContextHandler
does not exhibit the same issue but is too restrictive. I'll need something in between.It is a bug that contexts that match and could not be opened effectively (for any reason) block you from using the widget with that data? Probably. :) When this happens, the only solutions is to clear the settings.
The text was updated successfully, but these errors were encountered: