1
ENGLISH / Re: Canceling input for Source not working as expected
« on: April 16, 2026, 07:39:19 »
Hi,
OK I'll review the list.
Thanks.
For info, work in progress...
OK I'll review the list.
Thanks.
For info, work in progress...
Select language :
News:
The brand new Ancestris documentation is also here for you if you have any questions.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
FRANÇAIS / Re: Tri des médias dans la fenêtre comportant les icônes
« on: April 14, 2026, 06:45:39 »
Bonjour,
C'est possible, les tris peuvent se faire avec ou sans accent, minuscule ou majuscule.
Auriez-vous deux captures d'écran pour voir de quels tris vous parlez? La fenêtre de gestion des médias depuis Cygnus?
Si c'est le cas, le titre est trié en ne tenant pas compte de la casse, alors que les fichiers en tiennent compte.
Cordialement,
Frédéric
C'est possible, les tris peuvent se faire avec ou sans accent, minuscule ou majuscule.
Auriez-vous deux captures d'écran pour voir de quels tris vous parlez? La fenêtre de gestion des médias depuis Cygnus?
Si c'est le cas, le titre est trié en ne tenant pas compte de la casse, alors que les fichiers en tiennent compte.
Cordialement,
Frédéric
3
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 10, 2026, 18:00:14 »
Let me add this new functionality to our todo list. Could be interesting indeed.
Thanks,
Frederic
Thanks,
Frederic
4
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 09, 2026, 18:15:01 »
Yes you're right. Aries version 13 was inconsistent in terms of descriptions and types (I do not have the old code in front of me now but EVEN and FACT tags were treated by exception (because these tags have a mandatory value in Gedcom standard 5.5.1), hence the change. Version 14 removes this confusion and that explains why you end up with reversed entered data for EVEN tags.
Unfortunatelly to reverse the values you have to manually copy/paste the switch.
We cannot automate this switch but if you are ready to give me your gedcom file and tell me which fields need the switch, I can do it for you.
Cheers,
Frederic
Unfortunatelly to reverse the values you have to manually copy/paste the switch.
We cannot automate this switch but if you are ready to give me your gedcom file and tell me which fields need the switch, I can do it for you.
Cheers,
Frederic
5
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 09, 2026, 10:54:28 »
As far as I can see, you entered Military Operations in the description field of the event in Ancestris 13 and it remains in the description field of the event now in Ancestris 14.
So if if Military Operations was the type of event, it should have been entered the other way around.
So if if Military Operations was the type of event, it should have been entered the other way around.
6
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 09, 2026, 07:50:16 »
Hi,
Only Aries has changed the way some events display the description, not the Gedcom editor, and Ancestris has not moved your data, so the information displayed in the Gedcom editor is the information that used to be displayed in the gedcom editor.
Also, events that had both the description and the type did not change either. Only events which do not have a description property (BIRT, DEAT and a few more) and where the type was used for entering a description by Aries have now a type which is called a type and which used to be called a description before the change in Aries.
Bottom line is: your data should not be changed and has not been changed nor moved. The only thing is, if you used Aries for BIRT, DEAT, what you though was a description is a description and remains, but now it is called a TYPE because that's what it was written into inside the Gedcom file and the Gedcom editor. There is no other way to describe a birth in the Gedcom standard apart from using the TYPE field.
I hope that clarifies and sorry for the pats confusion, but again, no data is more incorrect in your file than it used to be.
Best regards,
Frederic
Only Aries has changed the way some events display the description, not the Gedcom editor, and Ancestris has not moved your data, so the information displayed in the Gedcom editor is the information that used to be displayed in the gedcom editor.
Also, events that had both the description and the type did not change either. Only events which do not have a description property (BIRT, DEAT and a few more) and where the type was used for entering a description by Aries have now a type which is called a type and which used to be called a description before the change in Aries.
Bottom line is: your data should not be changed and has not been changed nor moved. The only thing is, if you used Aries for BIRT, DEAT, what you though was a description is a description and remains, but now it is called a TYPE because that's what it was written into inside the Gedcom file and the Gedcom editor. There is no other way to describe a birth in the Gedcom standard apart from using the TYPE field.
I hope that clarifies and sorry for the pats confusion, but again, no data is more incorrect in your file than it used to be.
Best regards,
Frederic
7
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 08, 2026, 18:50:10 »
Please make sure you start with a newly created individual:
- Type if a category of description.
- Description is the exact event details as found in official source document
To my knowledge, this is now consistent across the editors.
If you reuse some existing individual events, it might be confusing because the data could have been entered the other way around.
Best regards,
Frederic
- Type if a category of description.
- Description is the exact event details as found in official source document
To my knowledge, this is now consistent across the editors.
If you reuse some existing individual events, it might be confusing because the data could have been entered the other way around.
Best regards,
Frederic
8
ENGLISH / Re: Canceling input for Source not working as expected
« on: April 08, 2026, 18:44:55 »
Hi Matjaž,
I do not see the unpredictability on my end. The cancel action cancels the last edition. If you do, undo, do, undo, happens what you think should happen.
If you do once, twice, then undo, it only undoes the last do.
In any case, if you have a normal editing sequence, it is a normal undoing sequence.
In order to help, the log file will not show any of this. But if you identify a sequence pattern which is not working as I said above, please just provide the sequence and I will investigate.
Best regards,
Frederic
I do not see the unpredictability on my end. The cancel action cancels the last edition. If you do, undo, do, undo, happens what you think should happen.
If you do once, twice, then undo, it only undoes the last do.
In any case, if you have a normal editing sequence, it is a normal undoing sequence.
In order to help, the log file will not show any of this. But if you identify a sequence pattern which is not working as I said above, please just provide the sequence and I will investigate.
Best regards,
Frederic
9
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 07, 2026, 19:06:09 »
This confusion has been resolved in Ancestris 14.
10
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 07, 2026, 18:33:43 »
Yes, try Ancestris 14 and see if it works for you as you would expect.
Regards,
Frederic
Regards,
Frederic
11
ENGLISH / Re: Proposal to add "Type" property in Aries editor
« on: April 06, 2026, 22:41:26 »
Hi,
in Ancestris version 13 is already there, just try adding a TYPE value from the Gedcom editor and then see where it has been added into Aries.
In Ancestris version 14, we have made it clear where it is.
Best regards,
Frederic
in Ancestris version 13 is already there, just try adding a TYPE value from the Gedcom editor and then see where it has been added into Aries.
In Ancestris version 14, we have made it clear where it is.
Best regards,
Frederic
12
ENGLISH / Re: Nickname display in Dynamic tree
« on: April 03, 2026, 21:05:53 »
Use the Dynamic Tree settings (top right button called "Configure View" (tooltip).
Go to the "Tuning" tab and change the box width/height.
Alternatively, change in that same panel the Box content zoom behaviour.
Regards,
Frederic
Go to the "Tuning" tab and change the box width/height.
Alternatively, change in that same panel the Box content zoom behaviour.
Regards,
Frederic
13
ENGLISH / Re: Nickname display in Dynamic tree
« on: April 03, 2026, 20:58:37 »<prop path=INDI:NAME?1:NICK format="{($e}"><prop path=INDI:NAME?1:NICK><prop path=INDI:NAME?1:NICK format="{)$e}">
Brilliant ! Thanks. I have just added this one in the documentation. https://docs.ancestris.org/books/user-guide/page/blueprints#bkmrk-cas-des-noms-%28propri
Frederic
14
ENGLISH / Re: Canceling input for Source not working as expected
« on: April 02, 2026, 21:19:08 »
Hi,
OK, I made a fix: (please check tomorrow)
- OK Cancel button remains. If only relates to the latest change within Aries. So, if you make a change in the source (1st change), then make a change in the note (2nd change), the note change validates the source change. Then, if you cancel, it will only cancel the 2nd change.
- The use of the Cancel button after the first change made in Aries no longer cancels a change made elsewhere by another editor before using Aries, which used to happen before this fix.
If this intented behaviour does not work, it means there is another bug somewhere. I tested a few things and it appears to be a stable and logical behaviour now.
I hope it will help.Let me know otherwise.
Best regards,
Frederic
OK, I made a fix: (please check tomorrow)
- OK Cancel button remains. If only relates to the latest change within Aries. So, if you make a change in the source (1st change), then make a change in the note (2nd change), the note change validates the source change. Then, if you cancel, it will only cancel the 2nd change.
- The use of the Cancel button after the first change made in Aries no longer cancels a change made elsewhere by another editor before using Aries, which used to happen before this fix.
If this intented behaviour does not work, it means there is another bug somewhere. I tested a few things and it appears to be a stable and logical behaviour now.
I hope it will help.Let me know otherwise.
Best regards,
Frederic
15
ENGLISH / Re: Automated Entry of "Type" when selecting a "occupation"
« on: April 02, 2026, 08:11:00 »
I was doing the same thing as Zurga, checking what the Gedcom specifications says.
To complement, I understand it could also be understood the other way around but the logic of the specifications seems to be a higher level.
My interpretation:
- For events with no description, it is rather clear, it "classifies" and distinguishes between 2 events of the same name.
- "Bishop" as a qualifier to ORDN
- “Stillborn” as a qualifier to BIRT (birth)
- “Civil” as a qualifier to MARR (marriage)
- “College” as a qualifier to GRAD (graduation)
- “Oral” as a qualifier to WILL
Now for events with a description, called "attributes", the question is legitimate but it should continue distinguishing 2 attributes of the same name (types of occupation, types of religions, types of residence, etc).
- For FACT, Zurga gave the example from the specification
- For OCCU, the specification does not say, but it should continue to be a type of occupation, as for other attributes, and the description text should then be the full occupation as written in the official documents of that person. Let's say the person was "Soldier in the 5th infantery regiment of the French territory army", that is what the description should say, and the type could be then "Military".
I hope this clarifies.
Best regards,
Frederic
To complement, I understand it could also be understood the other way around but the logic of the specifications seems to be a higher level.
My interpretation:
- For events with no description, it is rather clear, it "classifies" and distinguishes between 2 events of the same name.
- "Bishop" as a qualifier to ORDN
- “Stillborn” as a qualifier to BIRT (birth)
- “Civil” as a qualifier to MARR (marriage)
- “College” as a qualifier to GRAD (graduation)
- “Oral” as a qualifier to WILL
Now for events with a description, called "attributes", the question is legitimate but it should continue distinguishing 2 attributes of the same name (types of occupation, types of religions, types of residence, etc).
- For FACT, Zurga gave the example from the specification
- For OCCU, the specification does not say, but it should continue to be a type of occupation, as for other attributes, and the description text should then be the full occupation as written in the official documents of that person. Let's say the person was "Soldier in the 5th infantery regiment of the French territory army", that is what the description should say, and the type could be then "Military".
I hope this clarifies.
Best regards,
Frederic