On 2014/01/11 03:02, Brian/Support wrote:

> Have you ever looked inside one of the .usr files (they are plain text). All
> the report .usr files are just a list of cryptic numbers with an occasional
> path name, file name or people readable value. The program opens those files
> to write the options and reads the file when creating the report. What the
> numbers mean to the program are not documented without reading the code for
> the report or the option setup screen. Translating those into a user
> friendly report to print out would require quite some work. In some cases too
> there may be no easy translation. How do you translate a number representing
> a colour choice into something a human can understand when the colour
> palette is 16 million colours?

I beg to differ a little with your comments about the meaning of numbers.
Sensible programming standards would, at the very least, dictate a more-easily
remembered set of identifiers for these numbers. In effect these are enumerators
(in VB, C#, C++ terms). For example

Enum {
   January = 1
   February
     <etc>
   December
   } Month

Coding should then refer to Month.March rather than the number 3. Thus, the code
becomes self-documenting.

Also, assuming that Legacy 8 is based on .NET (a big assumption, but I do see
evidence of WPF having being used), then it is possible to convert the other
way, such that where a field, nominally defined as a Month, contains the value
3, the value "March" can be extracted. This would greatly simplify - but not
shorten - the task :-)

As for the names of colours, the main ones (not all 16 million) have been
assigned names by Microsoft. They read like a paint chart :-)

--
Regards,
Mike Fry
Johannesburg (g)



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


Reply via email to