Jon, I agree completely. And don't forget that it is not merely the issue of the humongous, but partially labeled, hot spots. As others have noted, there are numerous instances of hot spots that are not indicated in any way on the screen. Some of these merely control navigation to different screen views, but others actually UPDATE DATA even though there is NO label indicating that anywhere.
A bunch of cool features in a program may be nice, but, to me, data integrity is the most important and non-negotiable thing. I've spent countless time updating information on 7500 individuals, and I'm nowhere near done. It is not possible for me to periodically revisit every individual and reverify every piece of data to make sure that an invisible hot spot has not altered anything without my knowledge. I will be following these issues very carefully in whatever release Millennia decides to address them. If it is in Version 6, I will definitely be trying the free version before buying. I love Legacy, but if their response indicates that they value their right to quick-and-dirty code over my right to data integrity, then I will definitely have to start looking elsewhere for dependability. My data is far more valuable than any program that it is used with, and I would certainly hope that they agree with that. Bob -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Wednesday, December 15, 2004 12:10 To: [EMAIL PROTECTED] Subject: Re: [LegacyUG] Hidden "hot spots" I understand the rationale of "internationalizing" Legacy; the company has to grow its customer base and is wise to do so. However, that effort has created an unintentional side effect, namely, the invisible hot spots by which one can unknowingly change an attribute. It is true that various Windows applications have labels as part of the hot spot. However, I suspect those label hot spots tend to be limited to the visible label field. The problem Legacy now has is that those label hot spots can be larger that the visible label. It appears the programmers have to decided to maximize the label hot spot, visible or not, to accomodate how various languages spell a word such as "private." And, therein lies the problem. I would suggest that if it is necessary to have a standard field length for a label that is larger that the visible, character length of the label, then the label should not be a hot spot. The label field and the check box/radio button should be separate fields with only the latter a hot spot. Jon Raymond St. Paul Park, MN http://freepages.genealogy.rootsweb.com/~raymond Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
