|
By Nand - Monday, October 15, 2018
|
GenoPro 3.0.1.4 + Skins Update Package 2018-10-01 + Code update package 2018-10-13. I found it strange that there was no reaction when clicking on any of the entries of a Descendant Tree Charts list until I noticed the URL at the bottom left corner of my FireFox browser window:  Should that not read tree=ind00004.js
|
|
By genome - Wednesday, October 17, 2018
|
Yep, you are correct. looks like I updated the standalone HTML Descendant Tree report a while back, probably to overcome some more 'same origin' security issues in Chrome, but forgot to update the Narrative Report skin as well.
I have included a correction in the Skins update http://support.genopro.com/Topic38889.aspxI also noticed that non-local pictures (e.g. http URLs as in HP) were not displayed so this too has been fixed. Have also included your latest NL-BE kit in that update.
|
|
By Nand - Thursday, October 18, 2018
|
Status quo. I have removed all old skins, just to be sure, and unpacked the contents of "2018-10-17 SkinsUpdate.zip". After generating a report using the English Narrative Report and the English Descendant_Tree skin the results are the same. No chart is displayed and the link at the bottom of the window still contains a reference to the xml file. This was an out-of-the-box test. I just unpacked an ran the generator. No customisations whatever.
|
|
By genome - Thursday, October 18, 2018
|
I'll check that. I was having some issues with DropBox deleting my files. Maybe I didn't restore the correct versions.
DropBox really doesn't play nice when there is a junction point i.e. the linked Code folder in the Narrative Report. I decided to set DropBox selective sync and tell it not to sync the linked Code folder, but it then went on to delete some files from by Narrative Common\Code folder as well !!
|
|
By genome - Friday, October 19, 2018
|
I have double checked and it is working fine for me and Util.vbs has the fix in it. (scripts.js was missing from update but that had not changed. new update has it)
Just wondering it is a browser cache issue with you?
|
|
By Nand - Friday, October 19, 2018
|
We're getting closer. If I select the "charts" menu and click on a name in this list, nothing seems to happen. However, if I click on the tree icon following the individual's name, it works. The descendant tree chart is displayed. There must be a conflict of parameters somewhere.
|
|
By Nand - Friday, October 19, 2018
|
By the way, the "Descendants Tree Chart - Parameter Settings" interface has the same problem as the one mentioned in the Cannot load saved profile topic. If I select a non-default profile, the screen refreshes and reverts to the "defaults" profile, as soon as I hit the [ Load ] button.
|
|
By genome - Friday, October 19, 2018
|
Yes I have only fixed half the problem. I had completely forgotten about the Descendants Chart Index. 
Thank you for your patience, I am going to blame it on another 'senior moment'.
I'll look at the parameter settings issue too.
|
|
By genome - Saturday, October 20, 2018
|
May be 'third time lucky' with today's skins update.
Also noticed that with the descendants chart in the Narative Report the frame maximise/restore icons were not addressed correctly so I fixed that too. Plus some cosmetic changes to config params
|
|
By Nand - Saturday, October 20, 2018
|
Thank you. I'll give it a try today. First need to do some cleaning-up. Looks as if I have more versions than files. The people I'm writing about are all dead. So they don't mind waiting.
|
|
By Nand - Monday, October 22, 2018
|
It all looks OK now. Thanks. By the way, is there a reason why we use different dictionary.xml files for the '{EN} Descendant Tree' and the '{EN}Narrative Report' skins? Looks as if we could use the Narrative Report dictionary in both skins, no?
|
|
By genome - Monday, October 22, 2018
|
Different Dictionary files are used because of the restriction imposed by GenoPro's Report Generator. It expects to find Dictionary.xml in the root folder of each report skin.
A better design would have been to have a universal Dictionary for each language accessed by all report skins, but it is very unlikely that Dan would make such a change now. I guess we could use symbolic links to link Dictionary.xml from each skin folder to a common folder for each language. It would be a fair amount of work to merge the Dictionaries and test the result. Ideally the GenoPro installer would create these links but, as with the Narrative Report and its link to the Narrative Common\Code folder, it might be necessary to have a 'first run' script to establish the link for each report type.
|
|
By Nand - Monday, October 22, 2018
|
Sorry, bad question. I have no problem in copying the same Dictionary.xml file into different skin folders, I even prefer it that way. I only noticed the dictionary in the Narrative skin is different from the one in the Descendant skin, although it looks as if Descendant could do with a copy of the Narrative. In that case I would only need to maintain one Dictionary.xml file which I can copy into the different skins folders were needed. Hope you can follow my reasoning.
|