Closed emyoulation closed 3 years ago
Kari Kujansuu responds on Fri, Sep 3 at 3:32 PM (UTC−05:00)
Hi, about your Github message about custom filters.
I have succeeded in creating a tool that may help with this issue. See
https://github.com/kkujansuu/gramps/tree/master/addons/FilterParams
I have put this temporarily in the above Github repository, not yet with the other "Isotammi" tools. Maybe you can take a look and comment.
I was looking at the Color Preferences to see if the issue with Dark Themes could be resolved with a built-in feature.
Instead of the hard-coded colors, what do you think of using the preset Colors in Preferences? You could use "Background for Dead" for Male, Female & Unknown and Family nodes "Background for Married", then repeat. There are Light (default) and Dark schema.
Hi Kari.
I do not think that the following is something that can be done. But it seemed to be a good question.
In general terms, it seems like the Filter Gramplet is just a way of easily passing a value to a preset Custom Filter.
So if the user types in "I0031" for the Person ID in the 2nd row of the Filter Gramplet, it is similar to calling a Custom Filter with the rule "
People with id containing <text>
" but where the user does not need to open the Custom Filter, drill down a level to change that "<text>
" parameter value or to change from exact matching to RegEx pattern matching.It just gives a more interactive access to the "
<text>
" by moving the parameter entry. It moves from a deep drill-down to the top of the interface.So maybe there could be a Filter Gramplet for more interactive access to parameters for Custom Filters? Or that directly opens the SuperTool so that the Drill-down is compressed to 1 level before giving access to your 4 text boxes?
In the Filter Gramplet's current implementation of Custom Filters, it is not only painful to Change a parameter, the pain is multiplied when the same parameter is is used for a multi-rule or multi-stage Custom Filter. (For multi-rule example: get a Great-grandparent list of a person by finding the "
Ancestor of <person> not more than <N> generations away
" for the same person at 2 & 3 generations where only 1 rule can apply. Re-cycling the rule for a different<person>
means changing the same parameter in 2 rules.This is not a request... just a thinking point.
The core code for custom filter will need some refinement to simplify storing & sharing custom filters. A robust recipe book of custom filters could become far too large for a pop-up menu. (Might be able to shoehorn re-organization into leveraging a Custom type Note.)
So when the call for ideas to re-design the custom filter becomes a formal GEPS proposal, you might have already considered your recommendations.