I have just upgraded from 2.0.0.9 to 2.0.1.1

I noticed the first time that I opened my genogram that the User-defined date that I had set in the options had been deleted (I had it set at 1078, so the fact that some some people were listed as being nearly 1000 years old was a good pointer!)

I re-entered the date, and all the ages were now dislayed correctly. I saved the genogram and closed Genopro. When I re-opened it, my user date had been deleted again, and I had to re-enter it. This happens every time, and is very frustrating!

If this is not a bug, but instead a new feature, can I ask that the user date be stored in the genogram itself so that the correct date for that genogram is loaded with the file?

Alternatively, a fix for this so it behaves the way it did before would be really appreciated.

Regards,

John

Can you tell me what 'calendar' you use?  By the way, last week I made a silent fix regarding a very similar bug.  Can you download & install http://www.genopro.com/InstallGenoPro.exe again and let me know if you still get this problem.

I am using the normal western calendar. But I use Genopro to keep track of fictitious characters and their relationships for a novel that I am writing. The current year for the novel is 1078, so in "Tools > Options" I had selected 'Use user-defined date' and entered '1078'. This has worked ever since the beta's right up until 2.0.0.9.

Now I have 2.0.1.1, whenever I launch the program, whilst the 'Use user-defined date' option is still selected, the field for entering the date is blank, and I have to re-enter it every time.

I have several customers using GenoPro for writing novels.

You are right... time is flying. I had to write a new routine to read the date from the Windows Registry (where the 'user-defined date' is stored) because the old routine would read the date using the selected calendar.  The old code would work fine using the Gregorian calendar, but would produce an error with other calendar, mostly the Hebrew calendar.

Try entering 1-Jan-1078 instead of just 1078.  I took a note to support year-only dates for the next update.

Can I suggest (as I think I have before) that the 'User Defined Date' be stored with the actual genogram for the future? I have three on the go for the novel: one for 1078, one for 1053, and one for 1102. When I load one for a different year, I have to go and change the user-defined date in order for all the ages to be shown correctly. If this could be stored in the actual genogram (in much the same way as it remembers the last screen position), that would be even more useful!

Thanks again for a great program and excellent support.

Cheers,

John

The user-defined date is already a workaround from the original code to compute the age from the system clock and extending this to have user-defined dates per document won't be an easy fix.  There are many routines that have to be revised to support user-defined date per GenoMap or per document rather than a simple global variable.