Let me say something at the outset what may be uncomfortable to hear, L8 was released with fewer known bugs than L7.0 had when it was released and that L7.5 has now. This is just a numerical fact from the bug tracking system. We are just accustomed to the bugs in L7.5...
That does not say that L8 is perfect... that never happens... L8 testing and development had gotten to the point that among the testers, we were not seeing new data destroying bugs.
As a retired long time test manager, I knew the product was ready to be exposed to a wider audience. Millennia made that decision that the time was right, and, if you look back at this list from when L7.0 was released, you will see many more birthing pains then than we are having with L8.
When support got swamped with new orders, myself, and several of the other testers, have chosen to fill in here to help the user base with the birth of L8. It has been a full time, unpaid job for the past several days. ;-)
In your following message, you said: "I have posted re a few issues with v8 but theres a lot more. Reporting them all would be too time consuming."
If we are going to confirm them and get them sent to development, we need to know about them.
Lastly, I will report the default install location issue, but I will also repeat... you want to install Legacy in your C:\Program Files folder. Virtually no testing was done with Legacy installed anywhere else. I have alerted folks of this issue.
OK?
john.
At 03:07 PM 12/1/2013, C.G. Ouimet wrote:
Thanks John, I can confirm that
>
However This has revealed another issue with v8 (My list is getting very long). In previous versions, the Legacy Update defaulted to install the update in the folder where the existing version is installed. V8 defaults to C:\Program Files (x86\Legacy8 regardless of where v8 was installed.
A lot of stuff broken in v8. Memories of past Legacies Fix 1 thing, break 5 others. I am regretting upgrading!
C.G. Ouimet
Kingston ON
From: John B. Lisle [ mailto:[email protected]]
Sent: December 01, 2013 02:06 PM
To: [email protected]
Subject: Re: [LegacyUG] PP Alert Details Hang [was: Legacy 8]
Glenn,
All of the evidence points to this being some problem with customizations as not everyone sees it.
However, it seems to have been fixed with Build 356. I was seeing it previously and cannot reproduce it now.
john.
At 10:51 AM 12/1/2013, Glenn Woodman wrote:
My experience is that the program hangs when I "click to see details."à I get no run-time error.à à If I right-click, or shift-right-click, I am taken to the correct dialog boxesà However, if I left-click to see details (which I presume is intended to inform me of where the problem lies), the program hangs.à The only way to get Legacy to come out of it is to kill it through Task Manager.à Before doing so, I went through the check/repair file process and restarted Legacy.à No error messages came up.à Task Manager indicates that Legacy is not responding.à I've even tried waiting as much as five minutes to see if it would begin to respond again.à It did not.
I am running Win7, have the 8.0.0.355 build, and experienced no problems in downloading and installing the program.
Glenn Woodman
On Wed, Nov 27, 2013 at 11:06 AM, C.G. Ouimet <[email protected] > wrote:
I'm glad it works properly for you. I doesn't for some of us. I'm in Deluxe ...
C.G. Ouimet
Kingston ON
-----Original Message-----
From: Brian/Support [ mailto:[email protected]]
Sent: November 27, 2013 02:01 PM
To: [email protected]
Subject: Re: [LegacyUG] PP Alert Details Hang [was: Legacy 8]
The clicks all work for me in 8.0.0.353. I tried both with Legacy
8.0.0.353 running in Standard Mode (Where Potential Problems lists are not available) and in Deluxe.
In standard mode the click brought up a Deluxe only feature screen telling me potential problem lists are a deluxe feature. Right click and Shift right click brought up the screens to either exclude the problem for the individual or the main setting screen to change the criteria for the entire file.
In Deluxe mode the click produced the potential problem list instead of the deluxe feature screen.
The problems that I checked were:
1. a gap problem, child born more than 48 months after previous child (called from the PP indicator on the child in family view) 2. Burial date before death date (called by clicking on the PP indicator for the person as husband in main family view) 3. an event date after death date. (called from the PP indicator in the event list)
Brian
Customer Support
Millennia Corporation
[email protected]
http://www.LegacyFamilyTree.com
On 27/11/2013 1017, C.G. Ouimet wrote:
> 800.353 hangs when you do any of that ...
>
>
> C.G. Ouimet
> Kingston ON
>
>
> -----Original Message-----
> From: Kurt Kneeland [ mailto:[email protected]]
> Sent: November 27, 2013 09:59 AM
> To: [email protected]
> Subject: RE: [LegacyUG] PP Alert Details Hang [was: Legacy 8]
>
> As you said, when you hover over a pp icon, you get options to change settings. Do the Shift-Right Click and then go to the Gaps tab. Ã There you can change the soon or long after marriage, and how soon or long between children to be flagged as a problem.
>
> -----Original Message-----
> From: Teresa Goatham [ mailto:[email protected]]
> Sent: Wednesday, November 27, 2013 6:32 AM
> To: [email protected]
> Subject: Re: [LegacyUG] PP Alert Details Hang [was: Legacy 8]
>
> I even managed to get Legacy to crash trying to turn off a Potential
> problem - not sure exactly what I did, now though, and it has'nt
> happened a 2nd time (but I have turned more off)
>
> It seems strange to me that if I hover over the PP icon I get options to change my overall settings, but not to mark that particular possible problem as not an issue. Especially the gaps, there are loads I'd like to be able to switch off quickly; I know they're not a problem without clicking to see the details.
>
> So many I may just turn off reporting for the gaps, good idea, but the
> numbers used just don't work for much of my tree. I wish I could
> change them, e.g. at one time most of the working class in England
> (i.e. most
> people) were expecting a child when they married, so less than an 8 mth gap between marriage and 1st child's baptism was probably the norm, certainly very common. At other periods or classes it was rare, hence being able to the change from 8 mths would be useful.
>
> Teresa
>
> On 26/11/2013 22:31, John B. Lisle wrote:
>> Hi,
>>
>> This has seemed to be an intermittent issue that started late in the
>> testing cycle. Not everyone sees it, and it may only occur on certain
>> type of PP Alerts.
>>
>> Please email me privately with details of what you see.
>>
>> thanks,
>> john.
>>
>> At 04:18 PM 11/26/2013, C.G. Ouimet wrote:
>>> --snip --
>>>
>>> When clicking the Potential Problems icon in Family View or Pedigree
>>> View opens up Potential Problems which is good. But Clicking to view
>>> details, right clicking to exclude problems or shift-right clicking
>>> to change problem settings all result in Legacy hanging.
>>>
>>> Windows 7 ?
>>>
>>> C.G. Ouimet
>>> Kingston ON
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
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
