-
Notifications
You must be signed in to change notification settings - Fork 1
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
Switching from Persons to Events category throws an error #22
Comments
Retested with v 1.1.2 changing the Category menu from Family to Event. Note: the Status bar warns "No active object" so I selected a record in the Events view and tried switching FilterParams to Family & then back to Events. Same problem recurs.
|
Most probably you have an Event filter that refers to a nonexistent filter in another category. That situation was not properly handled after the recent changes. The latest version 1.1.3 fixes this by displaying an error message like "filter not found in namespace " in that case. |
Cross-posted to Discourse forum I can think of 2 specific ways that Custom Rules can decay:
Besides being referenced by name in the
This problem is similar to link rot for URLs. The project probably needs to:
Example reference by index: Example reference by type and index:
Example of Custom Filter referenced from within another Custom Filter:
|
If "a Custom Filter references an add-on query rule that is not installed" then Gramps discards the rule when initially loading custom_filters.xml. So this tool never sees such a rule! Nothing it needs to do!? |
That's good to know... but disturbing too. Now I have to experiment to see what happens. Will I lose all my libraries of SuperTool custom filters when 5.2 is released? It won't have any of the generic rule add-ons installed when run the 1st time. And I'll have to run it to install the add-ons. |
Switching from Persons to Events category throws an error
Switching to any of the other categories did not throw any errors
Id: FilterParams
Description: Display custom filters and allow changing their parameters
Version: 1.1.0
The text was updated successfully, but these errors were encountered: