"...using a single field for BOTH the radio button or check box and the label to the right of it (quick and dirty code) ..."
In the Microsoft Access Development Environment, the standard behavior for a bound 2-state control at create time is for the control AND its associated label to both receive focus and change state when clicked. There's nothing "quick and dirty" about it. I have clients who would have my head on a platter were I to disable that feature, as it simplifies data entry.
As I understand it, implementation of multi-language capabilities resulted in the introduction of extraneous whitespace where the English and foreign character strings differed substantially in size. Obviously, the law of unintended consequences came into play here, and the issue needs to be addressed. But just as obviously, the solution is not to simply resize the offending labels and reissue the software - THAT, would be "quick and dirty code", a tactic of hacks, which the Legacy programmers definitely are not.
Margaret
----- Original Message ----- From: "Bob Janetzko" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, March 02, 2005 8:16 AM
Subject: RE: [LegacyUG] priorities - was: Names
"This is the way checkboxes (and radiobuttons) work in Windows. Clicking the
label is the same as clicking the checkbox itself. I don't think the Legacy
programmers can't change this behavior"
Dennis,
That is not the case. People who know about coding PC programs (not me)
have stated that using a single field for BOTH the radio button or check
box and the label to the right of it (quick and dirty code) is what causes
the enormous (and unexpected) active area. If the entry spot and the label
are defined as separate fields, then only the entry area will be a hot spot.
The labels will be inert background, just as they appear to be on the
screen, and the huge blank spaces to the right of the labels will be
irrelevant. There is much discussion of this subject in the archives
a couple of months ago.
Bob
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
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.5.7 - Release Date: 3/1/2005
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
