The updated uimanager and managedwindow uses the plugin id to create actions for plugins that make a window to support the menus. If the plugin id contains a space, Gramps crashes.
Fixes#11202
After asking the OSM support, I was told OSM forward all http request to
https when we use .org url.
So it should work in all cases.
This has an energy cost, so it would be good for the planet to change
http to https.
* Avoid comma in a lat/lon entry field.
* Be more precise on the tooltip text.
* conv_lat_lon should not accept comma in lat/lon
* Tests failed with comma in lat/lon
* geoplaces fails to center if bad lat/lon
In this patch:
1 - If you copy/paste strings from another application,
you can add CR, LF, TAB and other special characters. I remove them.
2 - suppress all leading and trailing spaces for these entry field.
Check all values of an attribute type and not only the first one.
Check all values of an attribute type. If a person has several attributes with the same type/key the current behaviour is that only the first value is checked.
Example Person X Atrributes:
(Key=occupation: Value=farmer)
(Key=occupation: Value=soldier)
(Key=occupation: Value=smith)
=> Currently: Filter 'persons with attribut' (Key=occupation, Value=farmer) returns Person X, but no return of Perrson X for (Key=occupation, Value=soldier) or (Key=occupation: Value=smith).
=> After fix: Person X is returned for all three filter searches.
* Fix '_havechildren.py' person filter
Check all families of a person for children and not only the first family
* Update 'person_rule_test.py' and '_havechildren.py'
Correct number for persons who have children is 905
This tool is looking for place names with leading or/and trailing spaces.
It also looks for in the first name and surname.
For each entry which contains leading or trailing spaces,
a row is added in a treeview.
You can see where the spaces are for each row as the name is underlined.
If you double click on the row, you can edit the Place or the Person.
Fixes#10824
User can now add the following columns in the csv import file for a person:
- Occupation description
- Occupation date
- Occupation place
- Occupation source
- Residence date
- Residence place
- Residence source
- Attribute type
- Attribute value
- Attribute source
the corresponding events will be added to the person.
The user can put several lines for the same person if two occupations are known, one event per line will be created.
