The fixes pending in a new release is part of our bug tracking/reporting and we do NOT advertise that list. It changes as bugs are reported fixed, tested and bug reports are closed or reopened if the testing fails so it is a moving target. It is also not a text file it is a web site where the status of individual issues are recorded. I can say the issue in this case is in the next release from the status of that one issue.
You can see what is included when a new release is issued here: http://www.legacyfamilytree.com/RevisionHistory8.asp Brian Customer Support Millennia Corporation br...@legacyfamilytree.com http://www.LegacyFamilyTree.com On 14-Jan-2014 2:19 PM, Brian L. Lightfoot wrote: > I've seen this response to several problems that have been reported and the > fact that the remote support personnel are being told what's included in the > next patch is the very thing that I asked about two weeks ago. That idea > didn't seem to go over very well with Millennia support claiming it would be > too much of a requirement to take the programmers off task yet it appears > that such a text file of "What's In This Update" does exist. Why can't the > users see the planned upcoming fixes then so they won't have to report on > problems already in the queue? Am I missing something here or does such a > text file already exist? > > Brian in CA > > > -----Original Message----- > From: Brian/Support [mailto:br...@legacyfamilytree.com] > Sent: Tuesday, January 14, 2014 10:51 AM > To: LegacyUserGroup@LegacyUsers.com > Subject: Re: [LegacyUG] Shared event sentence > > It should work and the fact that it does not is recorded in our problem > reporting system. It has been fixed and will be in the next update to Legacy > 8. > > Brian > Customer Support > Millennia Corporation > br...@legacyfamilytree.com > http://www.LegacyFamilyTree.com > > On 14-Jan-2014 12:04 PM, Jim Christenson wrote: >> "This event was shared from..." >> >> Added to the end of every shared event gets old very quickly. >> Unchecking a checkbox in event options looks like it should work but does >> not. A bug? >> >> Jim > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
